on 07-24-2009 5:17 PM
Hi ,
We are using the classic scenario.
When we try and transfer purchase requisiton with no account assignment from ECC MM to SRM it dumps with the following error below in SRM . It fails in FM "BBP_READ_ATTRIBUTES ". In SMQ1 it fails with error " Exception condition "OBJECT_ID_NOT_FOUND" raised"
We can transfer other types of requisitons (non stock , freetext and services) successfully.
Exception condition "OBJECT_ID_NOT_FOUND" raised.
Error analysis
A RAISE statement in the program "SAPLBBP_ATTR_PDORG" raised the exception
condition "OBJECT_ID_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"RAISE_EXCEPTION" " "
"SAPLBBP_ATTR_PDORG" or "LBBP_ATTR_PDORGF01"
"MAP_OBJECT"
or
"SAPLBBP_ATTR_PDORG" "OBJECT_ID_NOT_FOUND"
or
"SAPMSSY1 " "OBJECT_ID_NOT_FOUND"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
Thanks
I guess we will have to develop a workeraround .. thanks for the information
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi leb
as per sap standard we may not push the purchase request into SRM eithout account assignment.
Moreover trick is that assign a duplicate account assignment for PR external request and assign the vendor in cockpit and strip the account assignment by BADI before PO creations in ECC.
please see the Justin thoughts.
br
muthu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.