on 07-08-2012 8:34 AM
Hi All,
System: SRM 701 and ECC- 603
As per requirement, i am uploading initial contracts to SRM from ERP. Once the contract is uploaded and released and sending back the same contract to ERP, so further call-offs (Ex: PO) will be created based on this contract.
I created contract with 1 line item in ERP, uploaded to SRM and released. In ERP side, BLAORD idoc is configured, so it will again proceess the same contract using FM: IDOC_INPUT_BLAORD. Problem here is, in ERP side it is creating additional line for the same contract (which was created initially in ERP with 1 line item. I would like to know, is this the std. behaviour or am i doing any thing wrong?. Any inputs are really appreciable.PS: If i check in the FM: IDOC_INPUT_BLAORD, it is using BDC and checks if contract exists then call ME32K, else call ME31K.
Regards VinothHello Vinoth,
Once the ECC Contract is uploaded to SRM, it has to be manually completed/cancelled/archived so that it is no longer used for call-offs. For all future call-offs, SRM Contract/Distributed contract in ECC has to be used.
In you case, I am not sure if you did this.
Also I think there is an issue with number ranges.
The internal number range of SRM contracts has to be maintained as external number range at the ECC contract doc type. There should be no overlap between internal number range of ECC Contracts with its external number range.
So whenever the SRM contract is distributed to ECC, it uses the same number of SRM Contract which is maintained as external number range in ECC.
If you follow these two steps, you issue should be resolved.
Regards,
Sushil.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vinoth,
As sushil mentioned the number range could be an issue, but since you are getting a new line item added to an existing Contract in ECC that means the number range has already been configured. Your problem could be the item numbering . The item numbering in SRM is different then in ECC.
In SRM it is 1 2,3 ... whereas in ecc it is 10,20,30. We faced a similar issue. We handled this in a BADI .
Please check this and let me know and I can give you further details on what needs to be done.
Regards,
Naveen
Thanks for inputs Naveen.
yes, you are correct. Problem with Item numbers only. I saw there is a check for item numbers in IDOC_INPUT_BLAORD. As item number is different in ECC and SRM, it is creating new item.
I am planning to use BAdI- BBP_CTR, method- MODIFY_DATA_CTR and eager to know about your suggestions too.
Regards, Vinoth
Vinoth,
Well in my case it was slightly different, as I was using NON PI web services for the transfer of Contracts and IDOCS for transfer of Scheduling Agreement. In my case the contract was working fine( as I was sending it from SRM to ECC via eSOA non PI webservices( you can access my blog to see how to incorporate it
but the SA had the issue that you have. Hence I placed the code in BBP_CTR , method MODIFY_DATA_CTR as you mentioned
You might have to do the following
1.From table t161 pick up the number range maintained in ECC ( so that you dont hard code as I totatlly hate it 🙂 )
2.Multiply ct_items each item by the field that you get in step1.
3.Also you will have to loop through the ct_cnd_hd and change the item number and VARKEY
4.Also loop throught ct_cnd_ct and change the item_number and VARKEY
5.And for ct_cnd_it just the item number has to be altered.
6.If you are using scaling then you will have to change ct_cnd_qs-item_number.
3 and 4 can get a little tricky as you might have to use offsets in your code in order to modify it.
Let me know if you still face issues, I will be more than happy to share more information. 🙂
Regards,
Naveen
Thanks for your quick reply Naveen.
I will let you know, if any issues. Do you have any update for my other query- http://scn.sap.com/thread/3206553
Thanks for your time.
Regards, Vinoth
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.