SAP SD issues and solutions. for freshers and experts

Hi SAPIANS,

I have worked on different types of Issues in SAP SD, Sharing my experience with you.

1.       Used SCC1 for transport the TR from one client to other client within one server (for example in development server – configuration client 100 and testing client 120).

2.       Used STMS_import for transport the TR from one client to other client between two different servers.

3.       Used tables, For

Sales order (VBAK- header data), VBAP- Item), VBEP- Schedule line), VBFA- Document type, VBPA- partner function, VBKD- Business data.

Popular Technical field name:

Sales org – VKORG, Dist. Channel – VTWEG, Division – SPART,

Plant – WERKS, Storage Location- LGORT, Shipping Point – VSTEL.

Sales document/Delivery/Billing. – VBELN, ITEM – POSNR, Sales document type- AUART

Base Uom – MEINS, Sales Unit – VRKME.

Customer group 1 – KVGR1, Material group1 – MVGR1, MENGE - Ordered Quantity by buyer.

Price group - KONDA

Delivery (LIKP- header), LIPS- Item),

Billing (VBRK- header), VBRP- Item),

Pricing (T683, T683S).

Customer Master (KNA1- General Data, KNB1- Company code data, KNVV- Sales area data,

KNKK- Credit management data, KNKA credit control, KNVP- Customer Partner.)

Material Master- (MARA – General Data, MARC- Plant data, MVKE – Sales area data,

MARD – Storage location data, MBEW/MBEWH – Material Valuation data,

Output Master (NAST), T code for configure – NACE.

 SPRO-> IMG-> Basic Functions-> Output Control-> Output Determination-> Output Determination 

Maintain Output Procedure screen – only 6 fields need to maintain

In the assignment of output data we assign the related document type to output with o/p procedure.

Sales activity type/sales document type/ billing type + Output procedure + Output type.

Credit management: KNKK, KNKA, T code- FD32, OVA8 screen.

VKM3/VKM4- Release SD document for credit check,

VKM1/VKM2- Display the Blocked documents.

Shipment Table:

VTTK- Shipment Header, VTTP- Shipment Item, VTPA- Shipment partner,

OIGS – TD Shipment, OIGSS

T code – VT01N, O4F1, O4G1, O4H1, MIGO, VI01,

Purchase order table – EKKO- Header, EKPO- Item.

4.       Used configuration and Customization for Enterprise structure,

Sales document type VOV8, Define Sales document Item category VOV7,

Item category Determination VOV4, - Sales Doc type + Item category group + usage +higher level item category.

Define Schedule line category VOV6, Schedule line determination VOV5 – Item Category +MRP Type.

Define Delivery doc. types OVLK, Define Delivery Item category OVLP,

Delivery Item category determination 0184, same as sales item cat. Determ. Except of delivery doc. Type.

Billing doc. type VOFA,

Sales document category

5.       Created Query with SQ01, it is used to join different tables in single place

6.       Used SE11- Technical field related to table, SE16 – Data browser,

SE09 – Display workbench request/Customizing request, SE91 – Error Message with class & no.

SE37 – Functional module, SE38 – Report/Program, SM30 – Customizing,

SM37 – Execute Background job, SU53 – check authorization for user.

7.       Used CMOD and SMOD transaction for customer enhancements and SAP enhancements for Check the required for suggesting ABAPERS.

For Example: -

A)     Adding one additional field as ship to party name in VA05 output report.

Hi you can see that price group is maintained at two place header data, and item data, so according to your requirement you can select query from VBKD table using sales order item data (VBAP)

 

Comment this part and then try

but here why did you kept the 1st condition

eq "00000'

that picks the data from header

can you comment that part and Then try

B)      Adding two columns in maintain billing due list – VF04

The enhancement V60P0001 by creating the include ZXV6PU08,                                                                     the structure VKDFIF and include ZXV6PU08, function module: SD_VF04_CALL_CUSTOMER_FUNCTION

Regarding the subject issue to add the columns: Material Group1, Price Group, Usage, Material and Material Description to the report VF04 output, the user exit EXIT_SAPLV60P_008 (Data Provision for Displaying Billing Index) in the enhancement V60P0001 has been amended by creating the include ZXV6PU08 and add the required code for columns addition, also the fields added to the structure VKDFIF (Billing Index), but in the execution time the program not enter the mentioned exit so that the columns appeared empty, to solve this issue the consultant suggest to raise OSS ticket because all the required steps are applied.

       Check document for detailed explanation.

Functional Specifications (FS) Documents

1.       Assigning storage locations to shipping points

What I have done in FS: I have Prepared FS Document with whatever the client requirement.

FS Document contains the Requirement description, Logic, advantage and disadvantage.

Solution:

In order to specify the rule for automatic determination of single storage location based on the shipping point in the delivery document, the Standard shipping point determination rule can be used, this can be tried using the standard SAP configuration. (Storage loc. determination OVL3, Shipping point determination OVL2)

a)     In order to apply the allow fixed list of storage for shipping point, the customer exit in SAP enhancement(SMOD) V02V0002 can be used for it

b) A Z table will be created for the combination of Shipping point and Storage location and default checkbox.

c) Shipping point will the key field and one of the storage location will be default while user should be allowed to maintain the other storage location

d) Transaction code should be assigned to maintain this table manually.

1. Create Table Z_ XXXXXX with following fields:

   VSTEL - Shipping Point

   LGORT               LGORT_D - Storage Loc 

   DEFLT BDL_DEFLT - Is Default?

   - Primary key (VSTEL, LGORT)

2. Create maintenance view for table and assign transaction code: ZSPPT_SLOC

3. in Function Module, EXIT_SAPLV02V_002

   Using field of importing structure, IF_LAGOF:

   Read the table, Z_ XXXXXX with key IF_LAGOF-VSTEL and DEFLT = "X"

   Get the LGORT for the above key and pass it to output structure, EF_LGORT

4. Validation of the storage location

Whenever user is trying to change the storage location in the delivery document VL01n or Vl02N following validation should be done.

The storage location entered in the transaction VL01N or VL02N should be as per Z table Z_ XXXXXX.  In this delivery document first find the shipping point LIKP-VSTEL.

Now for the shipping point in the delivery check the list of all allowed storage location as per table           Z_ XXXXXX

If the storage location in the delivery document is same as one of the storage location defined in the table Z_XXXXXX for the shipping point of the delivery then do not give any error message otherwise provide the error message as wrong storage location as per table Z_ XXXXXX.

This logic should be written in one of the below exit:

Validation for storage location: In include program MV50AFZ1

Two subroutines: USEREXIT_SAVE_DOCUMENT or                                                                                                                  USEREXIT_SAVE_DOCUMENT_PREPARE might help you.

2) Functional spec delivery creation + Piking + Post goods issue.

Data Upload-LSMW using BAPI rather than BDC recording.

ABAPER developed report ZSD_DEL_UPLOAD with functional module

For delivery - BAPI_DELIVERYPROCESSING_EXEC

For Picking - WS_DELIVERY_UPDATE

For Post goods issue - BAPI_GOODSMVT_CREATE_OIL.

Suggested required logic and code to develop report.

SAP SD ISSUES:

1.       accounting document not generating

Material account group wrong maintained by some user, so it was giving error.

2.       Created single delivery from multiple sales order – VL10A

Multiple sales order in one delivery if orders have same shipping point, ship to party & delivery date, route, Incoterms.

3.       Created single invoice from multiple delivery – VF04/ Invoice splitting.

1. Payer

2. Payment Terms

3. Incoterms

4. Destination country

5. Billing date

6. Actual Goods issue date

7. Foreign trade data

8. Billing doc type

9. Shipping conditions

10 Account assignment group of customer/material

11. Exchange rate

12. Billing relevance field in the item category

It will be combined into one Billing document automatically and this is controlled by the copy control.

4.       Zero Confirm quantity in Sales order/ Error in delivery "Zero Qty avalible of sepefic materail in ECQ 210"

Because Availability check was active in material master and Goods issue quantity was higher than goods receipt quantity. So it was giving error.

5.       Discrepancy in figures - Physical Inventory vs Finance

Developed Report RM07MMFI with SAP OSS Note. In SE38 to analyze the difference.

6.       Not updating Automatic pricing.

In Customer Master, Customer pricing procedure was blank.

7.       Standard Shipment process

https://blogs.sap.com/2013/08/06/standard-shipment-process/

8.       Accounting Document not cleared message after create invoice.

It is standard functionality only no need to worry about that once the payment receives by accounting people from the customer ,they will run F-28 - Post incoming payments or F-26 Payment past entry after that it will come to cleared status.

9.       Storage Location determination

Shipping point + Plant + storage condition (Material master – general plant data/storage view)

10.   Shipping Point determination.

Shipping condition + Loading group (Material master – general data/plant data) + Plant

11.   Route determination.

Departure zone (Shipping point) + Transportation group (Material master – general data/plant data) + Shipping Condition + Destination zone (Ship to party)

12.   Plant determination:

CMIR + Customer master + Material Master.