Showing posts with label SAP Notes. Show all posts
Showing posts with label SAP Notes. Show all posts

Wednesday, October 7, 2015

FI Substitution rule activation program RGUGBR00

In case, your Substitution rule is not activated in Live after transport movement, you may need to activate ‘main program’.
 
To do that, run below program.
 
Program : RGUGBR00  - Tick all options except last 2 and run for ‘FI’ application area

 
SAP Note: 842318  explains in detail

842318  

Friday, August 21, 2015

Packing status in Delivery header


Packing status in Delivery header will be changed to 'C' (Completed) though there are some items with out packing.

This is standard behaviour if the item category is set to (in 0VLP) 'Can be packed' - As it is not necessary for all items to be Packed.

There is a different setting in 0VLP called 'must be packed' - you can use this if you want header to be Completed only if all items are must packed.

SAP note (KBA) - 1508233 

Tuesday, August 11, 2015

Debugging Bdoc - 'Fill in all required entry' error case


SAP note:  1541354     (for issue saying 'Fill in all required entries')


It is possible to debug the upload as follows, in order to identify the required field:                              
  1. Display the BDOC in SMW01
  2. Enter /h in the transaction code field
  3. Press the 'retry to process message' button.
  4. In the debugger - select the Settings button and 'In background task  do not process' (Classical debugger) or for New Debugger, select from Menu: Settings and select "Change Profile Debugger/Settings" then mark flag for "TRFC (In Background Task): Block Sending" and click on icon "Enter".
  5. Enter F8
  6. Create a new session for the outbound queue (/osmq1) there will be an entry R3AUBUPA*** or CSA_BUPA**
  7. Double-Click on this queue entry twice and choose Debug for the CRM_UPLOAD_TRIGGER
  8. In the debugger, set a breakpoint at statement 'CALL TRANSACTION' and then press F8.
  9. At this statement double-click on the statement CALL_TRANSACTION and change the variable CALL_TRANSACTION_MODE from N to A, press the 'change field content' button and then press F8
  10. Now you will be in the R/3 System and you can see the batch input screen for this customer and you will then be prompted for the missing field in the BDOC.
When the field has been identified, please maintain this field in CRM.
Remark: In order to enter into debugging mode, you should ensure that the USER to connect to the R/3 system via RFC (txn SM59, Logon and Security tab), is set in your R/3 system as Dialog mode (txn SU01). Also RFC user must have debugging authorization.