SRM PO replication to backend ECC (Extended Classic Scenario)

[santhosh_shanig]

I would like to have inputs on this scenario, as which BADI we need to use and what we need to do exactly to replicate PO from SRM 5.5 to ECC 6.0.

Thanx and Regards

[santhosh_shanig]

HI Teja,

Thanx for ur reply. It is exactly ECS scenario, but in SRM we are creating Blanket PO and it is not conventional blanket PO, so to replicate this blanket PO to backend, what I need to do exactly in this case.......

Regards

Santhosh

[Former Member]

Hi Santosh,

in ECS the PO is replicated automatically to R/3 (as mentioned above).

If you like to change any data while transfering data to R/3, you could use the following BAdi:

BBP_ECS_PO_OUT_BADI

Best regards

Andreas

[santhosh_shanig]

HI

Thanx, Can you just pass on the relevant coding....

I have given rewareded points already...

Regards

Santhosh

[Former Member]

Hi,

just try out the following:

If you activate the BAdi, make sure to take over all Import params into your Export params!

Otherwise data may be lost!

Here is an example:

****************************

*-- data declaration

Data: wa_longext like line of ct_longtextt,

wa_item like line of et_item,

zw_index type sy-index,

zw_counter type ec_counter.

*-- take over all import data to exp params

es_header = is_header.

et_item[] = it_item[].

et_partner[] = it_partner[].

et_account [] = it_account[].

et_orgdata[] = it_orgdata[].

*-- Change data

*-- modify given vendor longtexts (ITXT) for example with a standard text

*-- for all positions

clear zw_index.

Loop at ct_longtext into wa_longtext.

zw_index = zw_index + 1.

if wa_longtext-tdid eq 'ITXT' ." Vendor Text

wa_longtext-tdline = 'Here your Text'.

modify ct_longtext from wa_longtext index zw_index.

endif.

endloop.

**********************************

*-- or if you would like to add a line of text to a position

*-- loop over positions and read text for vendor text

loop at et_item into wa_item.

clear zw_counter.

loop at ct_longtext into wa_longtext

where guid = wa_item-guid

and tdid = 'ITXT'

and tdspras = '???'." -> your language (E= English, D= German...)

endloop.

*-- if position contains vendor texts already, you know the counter index

*-- add 1 to counter to get the "new" index for your new line

zw_counter = wa_longtext-counter + 1.

wa_longtext-guid = wa_item-guid. "to combine the text with the SC position

wa_longtext-tdid = 'ITXT'.

wa_longtext-tdspras = '??'.

wa_longtext-counter = zw_counter.

wa_longtext-tdline = 'Your Text'.

append wa_longtext to ct_longtext.

endloop.

********************************************

This is just an example which I have coded right now.

Hopefully without any syntax errors.

Of course you have to adopt this coding to your requirements.

Best regards

Andreas

[santhosh_shanig]

Thanx

[santhosh_shanig]

HI Teja,

Thanx for ur reply, you mean that we dont have to do any coding or any config settings to replicate PO to ECC.

Thx

[Former Member]

Hi Santosh,

Exactly. In case you are using the ECS (extended classic) no need for any coding.

The P.O will be replicated to back end R/3 once you create it in SRM through RFC. And will be visible in R/3 in display mode. Changes not possible in R/3.

Same way if you craete the GR(Confirmation) and Invoice in SRM they will be replicated to R/3 through I.Doc and can be seen in the display mode.

Otherwise you can create the GR & invoice in R/3, in such a case the status gets updated in SRM.

Hope this makes you more clear. Clarifications are welcome.

Award points for suitable answers.

Rgds,

Teja

[Former Member]

Hi Santosh,

If you are using ECS (Extended Classic Sceario) the P.O created in SRM will have a copy in R/3.

There is no need to replicate the P.O. The P.O can not be changed in R/3. The change is only possible in SRM.

You can create the G.R and invoice either in R/3 or in SRM.

Hope this answers your query. Clarifications are welcome.

Award points for suitable answers.

Rgds,

Teja