on 07-05-2007 2:50 PM
HI,
1. I have created GOA in SRM which is transfer to R/3.But then I have locked GOA in SRM but the same effect is not getting replicated in R/3.Why this is happening? How to track that also?
2. How to track GUID number for any GOA as to run some BADI purpose.
Kindly do not send any links to trace the issues.
Thanks,
Navneet.
Hi Claudia ,
Thanks for reply.
But my prb is that I have already closed one GOA in SRM but the same effect hasnt been given in R/3, it means it is still open in R/3.So weather close option is also working like lockas u said?
But on what basis we can say that lock function is not work after GOA distribution? Becasue I have tried for some GOAs after distribution both Lock and close function is working properly.
Navneet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Navneet,
the lock of a GOA only works for the document till it is not distributed. For a
distributed GOA the lock does not have any effect. Option would be to copy the
existing GOA and create a new one and close the old one.
Cheers,
Claudia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Processing of GOA ->
1) Lock: Lock usage from other users; still there and visible. You can only lock a document if it has not been distributed
2) Delete: Deletion of the full document; makes sense when there are no POs yet
3) Close: Closes the document for usage; e.g. close before expire. eqivalent to close SC.
Related link ->
http://help.sap.com/saphelp_srm50/helpdata/en/43/0f23869e242a8be10000000a1553f6/frameset.htm
You need to call BBP_PD_CTR_SAVE after BBP_PD_CTR_CREATE (assuming the document is created successfully without any errors).
Use the importing parameter e_header-guid of BBP_PD_CTR_CREATE for the exporting parameter iv_header_guid of BBP_PD_CTR_SAVE.
The Transaction to create GOA with SAP Gui is BBP_CTR_MAINCC.
Try the BADIs using SE18 Transaction in SRM system
BBP_CTR_BE_CREATE Exit when Creating a Contract in the Backend System
BBP_CTR_INIT_UP BAdI to upload Contracts and GOAs to SRM
BBP_CTR_MAIL_BADI BAdI for Changes Regarding Sending Mails
BBP_CTR_MASS_BADI Implementation of Mass Change Parameters
BBP_CTR_STAT BAdI to enable changes in the contract status
-
<u>Also refer to the following function modules in the SRM system -></u>
BBP_CTR_MASS_APP_SORT_ORDER Creates the correct order for the processing of the contracts
BBP_CTR_NOV_CREATE
BBP_CTR_NOV_CREATE_V1
BBP_CTR_BID_EXT_CREATE Create contract from ext. RFQ without Sourcing
BBP_CTR_BID_EXT_SOCO_CREATE Create contract from ext. RFQ with Sourcing
BBP_CTR_BID_LOC_CREATE Create contract from loc. RFQ without Sourcing
BBP_CTR_BID_LOC_SOCO_CREATE Create contract from loc. RFQ with Sourcing
BBP_CTR_FROM_BID_EXT_CREATE Create contract from ext. RFQ
BBP_CTR_FROM_BID_LOC_CREATE Create contract from local RFQ
<u>Also refer to following links -></u>
Hope this will help.
Do let me know.
Regards
- Atul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.