on ‎2010 Apr 16 8:17 AM
Hello, when I try to activate extended classic scenario to create contracts in SRM and then transfer them to R/3 I have these options:
Extended local PO
BE Purch Grps Resp.
Back-end check reqd
Back-end errors, show as error msg
Which options may I have to select?
Thanks in advance
Request clarification before answering.
Hi,
Are you sure that this config you want to do is to create contracts and transfer to R/3? The settings you have mentioned are for Shopping Carts creation and being able to use the back end Purchasing groups on SC and PO's with out using the backend PO badi.
Please elaborate.
DV
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rosa Rodriguez,
If I remember correctly, you might need to create a global outline agreement and then the contracts would be distributed to single or multiple ECC systems. The intention of this functionality is to report the R/3 spend on the contract along with the SRM spend at a single place.
Please follow the link.
http://help.sap.com/saphelp_srm30/helpdata/en/7d/0a093f7c392e5ae10000000a114084/frameset.htm
Thank You,
DV
Hi,
I think it is not possible with Local contracts in SRM. You have to create a global outline agreement and then distribute this to single or multiple back ends. If your requirement is to transfer only one contract you should be able to use the BAdI "BBP_CTR_BE_CREATE" with your own implementation.
This will surely work till SRM 6.0.
Thank You,
DV
Hi,
I think Rosa's requirement is to create a manual and local contract in SRM. Indeed you mentioned an excellent BADi, but my understanding is this badi gets called from the sourcing application. I am not sure whether this gets called from the SRM local contract. This is the help documentation I am pasting here. It would be wonderful if this works. See the highlighted "importing parameters" part of the following pasted one.
Thank you,
DV
Determine Target System of Contract
Use
With method CONTRACT_LOGSYS_DETERMINE, you can control the target system determination for contracts.
In the standard, the Sourcing application and SAP Bidding Engine create contracts locally in SAP Enterprise Buyer . With this method, you can create a contract in the backend system instead.
Requirements
You are using a backend system with Release 4.6B or higher.
You have created the logical system in activity Define Logical System
Parameters
Importing
The BAdI takes this data from requirements in SAP Bidding Engine (bid) or from requirements in the Sourcing application.
IT_HEADER
Header structures
IT_ITEMS
Item structures
IT_PARTNER
Business partner data such as vendor or location
IT_ORG
Organizational data
Changing
In the method you can overwrite the following field:
CV_LOGSYS
Name of the system in which a contract is to be created.
If this field remains empty or contains the name of the local system, then the contract is created locally.
If this field contains the name of a backend system, then the contract is created there.
Notes
When coding the method, use the delivered sample coding as a guide.
See also
BAdI Determine Backend System / Company Code
Hi,
Are you sure that this config you want to do is to create contracts and transfer to R/3? The settings you have mentioned are for Shopping Carts creation and being able to use the back end Purchasing groups on SC and PO's with out using the backend PO badi.
Please elaborate.
DV
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.