Central Contract Distribution to Scheduling Agreement

[Former Member]

Hi Experts,

We are on SRM7,02 & EHP5.

I am looking for some information of distribution of scheduilng agreement, if it is with IDOC[BLAORD] or there is standard solution available to use ESOA.

Thanks

[Former Member · Accepted solution]

Hi Rohit,

As Sushil said it is via BLOARD and COND_A which needs to be configured in ECC in the distribution model.

There are a lot of issues in Scheduling agreement transfer ( item numbering and text transfer issues) so be prepared  🙂

Regards,

Naveen

[Former Member · Accepted solution]

Hi Naveen & Sushil,

Thanks for your inputs. It would be greate if you can share across the steps to configure in SRM.

Distribution Model (BLOARD and COND_A) has been set up in ECC. I don't see the document type assignment as we do for Contract.

Can ou suggest the missing step in ECC & SRM side.

Thanks

Rohit

[Former Member · Accepted solution]

For replication of contracts from SRM, config is minimal/none.

Make sure when you create a contract in SRM, you add distributions and select the right Porg,currency,plant,type as schedule agreeement.

ON the ecc side, you have to create a schedule agreement document type same as the contract type used in SRM. Also the number range used in contract of SRM should be configured as external number range for schedule agreement in ECC.

If you do not want same document type, you can always map using badi BBP_CTR in ECC or BBP_CTR_BE in SRM.

Additionally distribution model has to be setup which you have already done.

If you are planning on release aggregation at contract level in SRM, you have to add DELINS in ECC(outbound) and SRM(inbound).

If there are other data errors they will show up in IDOCS in ECC (WE05).

Thanks,

Sushil.

[Former Member · Accepted solution]

Hi,

We managed to distribute Scheduling Agreement.

Another challange is - Item level distribution tab is not allowing to select the backend document type.

Data is populated with default value Contract. Selection Option or selecting Scheduling Agreement is no more appearing.

Any clues !

Regards

[Former Member · Accepted solution]

Hi,

Have you implemented PPS functionality? If so , then that could be the reason. You might want to refer to note 1354971.

If PPS functionality is not activated, then you might want to check if you have activated all the Central Contract  related switches in SRM?

Regards,

Naveen

[Former Member · Accepted solution]

Hi Experts,

I would like to ask about the Delivery Schedule Release update to SRM Contract.

We are using document type LP which is being distributed from SRM CCTR. Which message type (DELINS or BLAREL) has to be configured for sending the updates back to SRM Contract.

What is the output type for Scheduling agreement - EL - LPET/LPFZ/LPE2/LPF2 etc.

Regards

Rohit

[Former Member · Accepted solution]

You have to use DELINS for release update to Contract.

BLAREL is for PO release update.

I have note worked with output for SA, but i found following sap help link.

http://help.sap.com/saphelp_470/helpdata/en/b7/286992ebc611d1b6400000e8a738dc/content.htm

[Former Member · Accepted solution]

Hi Sushil,

I did the setup for DELINS. Outbound IDOC is sucessful in ECC.

I don't see any inbound updates in SRM system. SRM Handles this via RFC or do we requires Inbound IDOC in SRM as well, if yes what is the relevant message type.

Thanks

[Former Member · Accepted solution]

Check BD64 in both SRM and ECC for DELINS.

[Former Member]

Contract distribution from SRM to ECC as a schedule agreement is still using BLAORD.  There is no ESOA interface available for this.

The document type config in ECC decides if the replicated document is a contract/schedule agreement.

The call-offs from ECC SA to Contract happens via DELINS type.

Thanks,

Sushil.

[Former Member]

Hi Sushil,

SA distribution looks ok now. another issue is about release updates to SRM Contract.

I have configured DELINS in WE20 for SRM LS with outbound parameters as-

Basic Message type - DELFOR02

Message Control  - EL

Message Type - ZLPT (Copy of LEPT)

Process Code - ME14

Change Box - Enabled

When I trying to add ZLPT "Maintain outgoing EDI-connection data for partner E24002"

What is the output type for Scheduling agreement - EL - LPET/LPFZ/LPE2/LPF2 etc. ?

Do we need to set up some thing in SRM as well ot it will be RFC call ?

am i missing some set ups ?

Regards

Rohit