on ‎2010 Jul 07 7:45 AM
Hi,
We are using SRM 7.0 as backend ECC EH4. I want to create Global Outline Agreement (GCTR) in SRM which will replicate on ECC but I donu2019t want to use PI so thatu2019s why I mentioned system type ERP_2.0 instead of ERP_4.0 in Define System Landscape because I donu2019t want to use CCTR.
Internal Number range in SRM and External Number Range in ECC for Contract is same. Document type GCTR defined in ECC and Transaction type in SRM is same. Defined Message type COND_A (process code COND) and BLAORD (process code BLAO) in ECC system as Inbound Parameters.
Badi BBP_CTR_BE_CREATE has been implemented in SRM for company code and
Badi BBP_CTR has been Implemented in ECC for mapping company code .
Same settings has been defined for SRM 5.0 and Contract has been replicated in backend system but in SRM 7.0 Contract is not replicating in ECC system as well as I am not getting any logs in WE05 , SMQ1 , SMQ2 , SLG1 , SMW01 , BBP_CTR_MON and RZ20 whereas in Contract Status it is showing RELEASED status.
In many threads I read that if system type defined in System Landscape as ERP_2.0 or ERP_3.0 then PI is not mandatory and Contract or Purchase Order created through Idoc / BAPI. Is it possible or not or if possible then which settings I am missing or which monitoring transactions I have to use , please suggest me.
Regards,
Abhijeet
Request clarification before answering.
Thanks soumik,
No I am not able to create Contract with SRM document. Due to external number range assignment system through following message u201CInternal number assignment not defined (please enter number)u201D.
Regards,
Abhijeet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Contract created successfully in backend and Item pricing conditions replicating in backend. Conditions I can see all conditions in Idoc , but I am not able to see this conditions in ME32K . For that which settings I have to perform? Please suggest me.
Regards,
Abhijeet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Muthu,
Now contract is create in ECC system. I deleted messages in WE05 and again add all messages.but contract condition is not coming in ECC whereas condition value available in IDoc.Please suggest me.
Regards,
Abhijeet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Muthu,
Thanks for reply. Actually we have server, budget and resources problem thatu2019s why we are trying to avoid PI. I am not getting any logs in Tx. BD87 and SM58.
Regards,
Abhijeet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
server, budget and resources - not understood well.
even SAP replaced old IDOC technology to PI ..
o.k
now lock the sm59 user in both side and see Queues are created or not after you approved the GOA .
you need lock both sm59 user before approve the GOA.
Let us see now queues are generated or not.go to stm outbound queue and see contract fm carries and awaiting or not
since it must work now since ECC EHP3 VS SRM 700 USES idoc technology
Muthu
Hi Arshad,
First i need to configure the GCTR because in SRM 5.0 we are using GCTR and then i will configure / test for the CCTR and i don't want to use PI .
Regards,
Abhijeet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SAP Note 1268821 - SRM 7.0 / ERP 6.04: Config. of Central
Contract Management
but your requirement is different
IDOC technology they want to replace to XI .
but why do you hate to do XI
do you have any specific reason for this?
ehp3 - idoc works well.
PS:- check any posting error in BD87 - 51 STATUS ERROR CODE OR
BBPD_CTR_IDOCREF - CAN YOU SEE ANY CONTRACT THERE.
Muthu
Hello Abhi jeet,
what about Contract Distribution?
Arshad
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.