Skip to Content
avatar image
Former Member

central contract not getting distributed to backend.

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Nov 17, 2009 at 09:32 AM

    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

    Add comment
    10|10000 characters needed characters exceeded

    • 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