Wednesday, 22 December 2010
Thursday, 11 November 2010
Tuesday, 28 September 2010
Important Tables for SAP SD
http://www.sap-img.com/sap-sd/important-tables-for-sap-sd.htm
Sales and Distribution:
Table Description
Customers
KNA1 General Data
KNB1 Customer Master – Co. Code Data (payment method, reconciliation acct)
KNB4 Customer Payment History
KNB5 Customer Master – Dunning info
KNBK Customer Master Bank Data
KNKA Customer Master Credit Mgmt.
KNKK Customer Master Credit Control Area Data (credit limits)
KNVV Sales Area Data (terms, order probability)
KNVI Customer Master Tax Indicator
KNVP Partner Function key
KNVD Output type
KNVS Customer Master Ship Data
KLPA Customer/Vendor Link
Sales Documents VBAKUK VBAK + VBUK
VBUK Header Status and Administrative Data
VBAK Sales Document - Header Data
VBKD Sales Document - Business Data
VBUP Item Status
VBAP Sales Document - Item Data
VBPA Partners
VBFA Document Flow
VBEP Sales Document Schedule Line
VBBE Sales Requirements: Individual Records
SD Delivery DocumeLIPS Delivery Document item data, includes referencing PO
LIKP Delivery Document Header data
Billing Document VBRK Billing Document Header
VBRP Billing Document Item
SD Shipping Unit VEKP Shipping Unit Item (Content)
VEPO Shipping Unit Header
Wednesday, 15 September 2010
Friday, 16 July 2010
Friday, 2 July 2010
Tuesday, 29 June 2010
Idoc - Batch Job for Reprocessing and other details
By: Mohamed
Check these reports:
RBDAGAIN - Process Outbound IDocs with Errors Again
Description: This report reprocesses outbound IDocs which contain errors. IDocs containing errors have one of the following statuses:
02: Error transmitting data to port
04: Error in EDI subsystem control information
05: Error in conversion
25: Continue processing despite syntax error (outbound)
29: Error in ALE service
RBDAGAIE - Reprocessing of Edited IDocs
Description: This report reprocesses an edited IDoc in inbound or outbound processing. The edited IDoc has one of the following statuses:
32: IDoc edited (outbound)
69: IDoc edited (inbound)
RBDAGAI2 - Re-processing of IDocs after ALE Input Error
Description: You use this report to reprocess inbound IDocs containing errors. IDocs containing errors have one of the following statuses:
56: IDoc containing errors added
61: Continue processing despite syntax error (inbox)
63: Error passing IDoc to the application
65: Error in ALE service
----
For Inbound
1) Goto WE19, select ur IDOC and execute. The details will be shown of IDOC. Change the data in the segment as per your requirement.
2) Click on standard inbound process. If you want to execute the process in foreground, click on standard inbound function module. Select related function module and execute the process in foreground/background.
For outbound
1) Follow same step 1.
2) Click on standard outbound processing
-----
To reprocess Idocs in outbound or inbound you can create back ground jobs using the following programs.
For Outbound:
For 02 status IDocs follow the below procedure:
1. Open SE38.
2. Give program RBDAGAIN.
3. Give you Idocs and save as variant.(Give any name)
4. Now, go to SM36,and specify a job name(Any name).
5. Now click on STEP give your Variant name in the respective field and you program name as RBDAGAIN.
6. Save and come back.
7. Now click on "START CONDITION".Here you give schedule the job either "Immediately" or "Periodically".
8. To do an immediate job select Immediate and save.Else go for perodic as you need.
9. Now save the screen on SM36.
10. To release the job click "Job selection" -- > select sceduled --> execute.
This would push your Idoc from *02*(Error passing data to port) to 30(Idoc ready to dispatch) status.
Now to send the Idoc from 30 to *03*(Data passed to port OK) use the "RSEOUT00" program and run another job as stated above.
This would send the Idocs to 03.
Similarly at Inbound side:
To reprocess an Idoc in 51 status:
Use program "RBDMANI2" and run a job.It will push Idocs from 51 to 53 status.
For 64 status use "RBDAPP01" program.
You can do it in transaction code BD87
-
Converting External Customer Number To Internal Customer Number – SAP EDPAR Table Have you ever had a project where you are converting a c...
-
FU BAPI_PO_CREATE1 ____________________________________________________ Short Text Create Purchase Order Functionality Function ...
-
How to implement BADI to change a Purchase Order - Post-processing to ME21N Written by PAS Requirement: Populate EVERS [ Shipping Poin...