Common Configuration SD

Common SD CR maintenance / fix :

 

1.      Output condition record

There are 3 output condition records in SD module : sales output (t-code VV11/VV12/VV13), delivery output (t-code VV21/VV22/VV23), billing output (t-code VV31/VV32/VV33).

Usually user will create CR for us to maintain new output condition or change existing one, in this case we’ll need to apply temporary id to maintain directly in JVP. Here is the profile we use (need to get approval from Sri and Atul, then submit SMI) :

-         TMP:VV31:03 (to maintain billing condition)

-         TMP:VV21:01 (to maintain delivery condition)

-         TMP:VV11:01 (to maintain sales condition)

 

We need to complete section 5 & 8 with “MANUAL” for Transport Request #, and request transport team to complete section 12 with MANUAL after getting approval for JVP.

Sample CR : 34228, 34094

 

 

2.       Table maintenance

There are table which will pop up the transport request automatically when we maintain in JVD, and there are which is not (but we still can transport it in case there is no other way to maintain directly in JVP, by creating transport of request).

-         Table which generate Transport request #

Sample : CR32493, maintain table Y9AFZZ

Transaction SM30, after maintaining new entry and it pop up transport request #, generate new one (create request) and put CR and description, then save. Later you can track your TR# in SE01, and release it accordingly.

 

 

We can see the object and value of key fields by choosing the lowest TR# and choose display object list.

 

 

 

 

 

 

-         Table which don’t generate transport request number

Sample : CR # 32843, table Y9ITT

Transaction SE16, after executing hit create, then save the new entry.

 

To transport, we create transport of copies by SE01, hit create and choose transport of copies.

 

 

 

 

 

 

 

 

Put description and target (don’t forget to put target system otherwise it will cause transport stuck and it will affect all transport from JVD to JVI).Then save.

 

After that, click display object list and add the object (click change and add new entries). For table program id R3TR, object TABU, and object name is the table name. Once created click on the object to create the key list. Choose insert line, and click on the line and fill up the table line that you want to transport, then save. Transport of copies will only have 1 number which we need to release.

 

 

 

 

 

 

 

 

3.       Standard text maintenance

User usually create this CR as they don’t have access to maintain standard text directly in JVP. We need to maintain in JVD, then transport to JVI and JVP using transport of copies (procedure creating transport of copies see number 2). Currently standard text is mostly used to print some text in invoice based on some condition (for example if it’s maintained in specific table for specific plant, then print the text).

Sample CR : 32843

T-code to maintain standard text : SO10

Depend on user request choose create or change and put text name, text id, and language as mentioned in the CR.

 

Update the text content as requested in the CR and save.

 

 

 

 

 

 

 

Create transport of copies, below is the object name (no key), change the second part of object name as the text name.

 

 

 

 

4.      Change address of plant or shipping point.

Sample CR 32119

Configuration path :

-         SPRO -> Enterprise structure -> Definition à Logistics general à Define, copy, delete, check plant à Define Plant

Choose the plant, and click Address, make necessary changes, you can review how it will be shown in the output (we are using SAP standard to show plant/shipping point address in the output) by clicking preview in the bottom of address.

 

Configuration path :

-         SPRO -> Enterprise structure -> Definition à Logistics execution à Define, copy, delete, check shipping point à Define shipping point

Choose the shipping point, and click Address, make necessary changes, you can review how it will be shown in the output (we are using SAP standard to show plant/shipping point address in the output) by clicking preview in the bottom of address.

 

 

5.      Shipping point related configuration

No shipping point determined for combination of plant and shipping condition.

Sample CR : 33912

Configuration path :

-         SPRO à Logistics execution à shipping à basic shipping functions à shipping point and goods receiving point determination à assign shipping point

Maintain the combination needed, proposed shipping point will be determined automatically in sales order, while manual shipping point will allow user to choose manually.

Table for this shipping point determination maintenance : TVSTZ

 

 

 

6.      Plant related configuration

No plant determined for specific sales area.

Sample CR : 33541

Configuration path :

SPRO -> Enterprise structure -> assignment à sales and distribution à assign sales organization –distribution channel – plant

Assign the specific plant to combination of sales org/dist channel, by doing this the plant will be allowed in the sales order.

 

 

 

7.      Pricing related configuration

Pricing determination configuration

Sample CR : 32227, 34042

Configuration path :

SPRO à Sales & distribution à basis functions à pricing à pricing control à define and assign pricing procedure à define pricing procedure determination

       Maintain the combination as needed

           

           

 

 

8.      Text configuration, direct config in JVP

Sample CR : 33836

Need to open JVP client to do direct configuration. For testing open JVI client first, get approval from Senthil mention specific date and time then forward to basis team. For JVP open client get approval from Sri, mention specific date and time then forward to basis team.

Configuration path : SPRO à Sales & distribution à basis functions à text control

Do configuration as needed, below is sample for CR 33836.

 

 

 

9.      Need to fix or modify output

Sample : CR 33843

Get the program and form name of the output using table TNAPR, then mention to developer these information and what need to be changed. If the changes are needed only for specific plant or output type, remember to restrict it.

 

Transaction to check program : SE38

Transaction to check form : SE71

 

10.  Need to fix report

Sample : CR 33883

Get program name of the report, then mention to developer what need to be changed.

 

 

 

 

 

 

 

 

12, To make "Customer" as field option so that user can input multiple customers in VK12.  Refer to CR34866.

 

User want a multi input for Customer in the key combination customer/material (No Hierarchy), the same as the material options input,

 

 

 

 

 

 

Go to IMG, Sales and distributionèbasic functionsèPricingèPricing ControlèDefine condition tables

 

 

 

 

 

TO select the field for Customer same as Material.

 

 

 

 

 

after change,

 

 

 

VK13 to confirm the change.