Skip to Content
avatar image
Former Member

SRM GOA not generating IDocs to transfer into ECC

Hello Gurus,

I Have been trying to configure GOA contracts to transfer into ECC. We have SRM 5.0 and ECC 6.0.

Our SRM 5.0 is Classic Scenario where we create Shopping cart which then convert into Bid Invitation - Bids and after that GOA

gets converted from successfully / Accepted bid.

The problem is whenever Contract get released from accepted Bid it should distribute into ECC as we have defined ALE structure with BLARI outbound IDOc from SRM to ECC and similarly BLORD & COND_A message type as Inbound in ECC.

Could you please let me know what settings I am missing to have this contract distributed.

Thank you in advance for your help.

Regards

Ritesh Raithatha

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

6 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 01, 2009 at 05:05 AM

    Hi Ritesh,

    Whenever the contract is released, it should create a idoc with message type "BLAORD" in ECC.So, checked the Idocs with type "BLAORD" in ECC giving the correct date in WE02.You will find the reason why it has not replicated.

    In ECC system

    Maintain outbound parameters for Message type BLAREL

    Inbound parameters for BLAORD and COND_A.

    Regards,

    Sheetal

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello, Muthu, Saravanan, Sheetal, Justin,

      Thanks a lot guys for your help. I have resolved with your valuable inputs. I was making mistake through Process contracts i was creating GCTR but its configuration in Define transaction type was changed by someone in our team to look like contract.

      Now successfully able to create IDOcs which in turn currently failing due to incorrect mapping logic.

      Thanks once again for all.. I will go ahead and close the thread.

      Best Regards

      Ritesh

  • avatar image
    Former Member
    Sep 30, 2009 at 05:16 AM

    Hi,

    Please maintain the following settings in ECC.

    1. SPRO - Material Management - Contract - Define Document types with external number assignmnet.

    2. SPRO - Material Management - Contract - Define Number Ranges with external ind ticked.

    Next you need to maintain the technical settings related to message types ( BLOARD & COND_A) in ECC & SRM .

    In ECC, BLAORD and COND_A will be inbound parameters.

    Hope this is useful.

    Regards,

    Sheetal.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi ritesh

      do you have any conditions in the item if it so remove for testing.

      CREATE A NEW CONTRACT with out conditions and distribute to porganisatin at header level and release the contract .

      now you may get an error in BD87 51 idoc error after released and approval (if you have approval process).

      you must get some error for first time since contracts dont have company code . so you need t take care of this by mappping in badi via porg level

      update me an error in bd87 51 error

      br

      muthu

  • avatar image
    Former Member
    Sep 30, 2009 at 04:39 PM

    As mutha mentioned, make sure you are filling out distribution tab with valid information and clicking the release button. If you are then try the following:

    Make sure the O1CT pricing condition is setup in backend and your pricing procedures allow the use of O1CT

    Check your default currency (system configuration, not at transaction level) in define currencies

    If you run FM B46B_CTR_TRANSFER with the guid of GOA and backend source system it will give you an onscreen error, if not debug that FM.

    I expect this FM will probably be in the outbound queue with status failed based on your problem description.

    idocs for contracts are not generated in SRM.

    Blarel02 is used to update SRM with release values and quantities from backend. Blarel02 is not part of contract distribution. When a contract is released and distributed to backend, and a po is released against contract, blarel02 is sent to srm to update the release quantities/values against contract.

    Blaord and cond_a are for contract distribution. This is the first thing you should look at, but sounds as if you are confident this is setup correctly. B46B_CTR_TRANSFER is your friend.

    Justin

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 02, 2009 at 04:10 PM

    To add:

    What you are describing is, in the outbound queue the FM B46B_CTR_TRANSFER is in status of sysfail. Any GOA distributed will queue up behind the sysfail and never be executed.

    Distributiion high level process:

    After GOA is distributed (the release button is pressed)

    SRM

    B46B_CTR_TRANSFER is executed, and maps fields to transparent table and transfers this to R3 using:

    R3

    BBPV_CONTRACT_TRANSFER (there is where the transparent table is mapped to idocs and idocs get created).

    FM BBPV_CONTRACT_TRANSFER is the link bwtween SRM and R/3. The is not an ALE process. it is an RFC technology done through BBPV_CONTRACT_TRANSFER. idocs are not passed from SRM to R3. If you are not getting any idocs and your distribution model is correct, then the problem is with B46B_CTR_TRANSFER on the SRM side. If you are getting idocs then following idoc troubleshooting described in this thread.

    If you click release in GOA screen and B46B_CTR_TRANSFER is not in the outbound queue, then it passed this FM successfully and you can rule it out. I expect the reason you are not recieving errors in contract distribution monitor is because its failing before it ever gets to the R3 FM BBPV_CONTRACT_TRANSFER which is where the idocs are created and this application monitor is updated by the backend errors. I say it nevers getting to R3.

    If you find B46B_CTR_TRANSFER is status sysfail in the SRM outbound queue then run it manually in the foreground and you will recieve your error. If not in the outbound queue, you need to concentrate on BBPV_CONTRACT_TRANSFER on the R3 side. If you not getting idocs you should run through the process step by step, troubleshooting each step and ruling it out before moving to the next step. I would also suggest you check your pricing conditions. SRM uses O1CT by default, and R3 uses PB00 by default, this will cause the behavior you are describing. ECC may have O1CT, i do not know. I hope helps.

    JF

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 05, 2009 at 08:46 PM

    Test

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 05, 2009 at 08:47 PM

    Closing the thread

    Add comment
    10|10000 characters needed characters exceeded