Schedule lines tranfer from R/3 to SUS in a MM-SUS scenario

[Former Member]

Hi SRM gurus,

We are working on the MM-SUS scenario where the scheduling agreement is created in the backend R/3 system. Delivery schedule lines are generated in the backend and transfered to the SUS thru. ME9E transaction for sending the delivery schedule to the SUS.

We have a confirmation control key which guides us in SUS to create an ASN in the backend.

Though there is a confirmation control key exist in the SA for that particular line item, when the ASN is sent from SUS to XI to R/3. There is an idoc error in the R/3 which says that there is no confirmation control key though it is there for the line item which is transfered to SUS.

Now Pls. answer my questions :

1) Will ME9E transfer the total lines in the SA or the schedule lines with the delivery schedules only ?

2) Is it possible to resend the same schedule line ( with the updated delivery schedule) to the SUS as per the standard scenario?

3) In the SUS how do we findout the materials corresponding to that particular delivery schedule line. Because in SUS the reference is only the scheduling agreement number as we could not see any scheduline line item.

Pls. suggest.

We are working on SRM(SUS) 5.0 with ECC6.0 as the backend.

Best regards,

Sridhar.

[Former Member]

Hi all,

We could observe the following in SAP R/3 MM for the sending the delivery schedule lines to the SUS vendor.

1) When we send the delivery schedule lines for the first time all the lines are being sent to the SUS. ( ME9E)

2) If we create a new delivery schedule for the same scheduling agreement ( ME38) and do ME9E again thru the ALE output type then the previous delivery schedule lines are also sent to the SUS vendor.

Is there a way to block this by which the SAP R/3 MM system will allow only the added delivery schedules to the SUS vendor.

If something can be done in coding by the changing the standard processing routine or If there is a BADI for the same kindly let me know.

Thanks in advance.

Best regards,

Sridhar.

[khan_voyalpadusman]

please check for the BADIS under th SUPPLIER sELF SERVICE SECTION.

there are number of BADIS available -->

look for BADI ---> Filter for sceduling agreement releases .

But i am not sure wether this will help..

But as far as i know the system will again consider all the lines ---> since it is updating again the same document...

[Former Member]

Hi Khan,

Thanks for the help and I am trying to find one but could not get anything useful.

Best regards,

Sridhar

[khan_voyalpadusman]

i have seen the code --> where the FM is called for creation of SAR in SRM.

that is FM

BBP_SAPXML1_SUSPO_CREATE_IN --> in this --> search for this

• Call API

IF ls_header-description EQ 'DELINS'.

CALL FUNCTION 'BBP_API_SUSPO_CRT'

EXPORTING

is_header = ls_header

it_item = lt_item

it_attach = lt_attach

it_partner = lt_partner

it_longtext = lt_longtext

it_tax = lt_tax

it_limit = lt_limit

it_sdln = lt_sdln

IMPORTING

es_header = ls_header_e

this one creates ---> the SAR in SRM.

and also i have seen further --> there is no place where any BADI is also called.

i am afraid it is not possible to control what you want using BADI.

only --> difference between --> New document and the old document is

the Indicator --> C for create

U for update.

And Also if you can see the XML message for the updated document --> you can see all the lines in the XML message.

Not the added lines...