on 11-17-2009 9:26 AM
Hi all,
We are working on SRM 7.0 and backend ECC6, however we tried to created a central contract it is not getting distriubted to backend.
we checked the transaction types and number ranges both SRM7 and backend no issues regarding that, and maintained the IDOC message type BLAREL also in both the systems, but still the contract is not getting distributed to the backend system.
Could any one among you suggest or advice us what can be done to achieve this target.
I appreciate your quick response.
regards,
IGA
Hi
BLOARD IDOC must have created in ECC after you release the contract in SRM system.
bd87
for today data
BLOARD - MESSAGE TYPE
How many contract created to day after you release the contract?
check queues smq1 /2 for contract oriented fM in srm side.
make ensure that connections between both systems.
BLAREL - is from ECC to SRM - Release values
br
muthu
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 your immediate rresponse.
Idoc with BLAORD message type has been already maintained in the backend system.
when I checked in WE20, I found that it has been maintained in inbound parameters, and before creatin of the cental contract it has been maintained in ecc sysem.
can you please let me know whether the BLAORD should be maintained in both the systems or only in ECC, if so in which system as inbound paramaters and in which system as outbound parameters.
regards,
IGA
HI IGA
Whenever you release contract from SRM to ECC , BLAORD AND COND messages will be created by RFC .
thats why i requested you to check Contract BLOARDs are reached to ECC.
moreover check rz20 conract error
bd87
bloard
51 status code
once you identified the failure reson you can correct and distribute again
br
muthu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.