New SNC PROACT scenario

[Former Member]

We have started to use long term planning in ECC for mid to long term demands.

This means that we in the active version only want to plan in the short term window.

We therefore will become problems in delivering a forecast to our vendors in SNC that goes further than the short term period.

Therefor we plan (have cerated) to create a new key figure in SNC where we will show demands from long term planning. We will still show the short term demand (important - means that we can't use the "old" one).

We have in ECC written a program that extract all the long term demands and puts the data into a PROACT idoc. The only difference is that we have a new qualifier to the demand type.

In PI we then take this qualifier and appended it as a copy to the item line of the standard and has given it the name "LongTermPlanning" in the productactivitynotification_in.

 
In SNC

We have made a new key figure in the order forecast Details - Product View .

We have used the guid http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0b0e544-7a06-2d10-539d-f8648358b...

Our challenge now is to get the XML message to from the inbound message to the shown key figure.

Is there a guide on how to do this or can you give a hint on how to proceed?

Regards,

Hans d:-)

[former_member584935 · Accepted solution]

The PI system place data in receiver system,  in a RFC queue.

After RFC queue data, input is stripped from XML  and placed in a nice SAP table structure=/SCA/BIF_MD_PROACT_NOTIF

The receiver system should have structure=/SCA/BIF_MD_PROACT_NOTIF regenarated after PI-system have made the his changes.  This knows all PI persons all about.

Goto into receiver system SCM system, in SE80 and chose display "enterprise services browser"
browse to "SNC 7.01", it is the service for the SCM system,
chose "Service interfaces"
CHOSE "ProductActivityNotification_In"
LOOK IN Provider Class        /SCA/CL_BIF_PROACT_IN
fIRST STATEMENT IN METHOD IS:  "ls_input = input". IT IS THE MULTI-LEVEL ABAp TABLE,
IT IS THE RESULT AFTER THE xml-input HAS BEEN STRIPPED, BY THE SERVICE/SYSTEM CLASSES,
FROM HERE IT IS JUST TO FIND SOME badi'S

Debug would be a good idea, be aware he is running with background user "PI_RFC" in our case.

You could also use the SM50 eternal loop trick.

Or be logged on as PI_rfc user

tECHNICAL NOTES:
Use these 2 BADI's
Badi= /SCA/BIF_I_PROACT method=AFTER_CONVERSION
BADI= /SCA/TS_EXCEPT method=TS_EXCEP
first BADI, Add new input tables, to timeseries-table
Second BADI, New timeseries-table are given a new key

It is a little clumpsy, but in the input there is no code field telling us something about the content,

so we have to recognize via the "TAG" name.

Hope these princips it helps