cancel
Showing results for 
Search instead for 
Did you mean: 

Does APO support the simplified CrossCompany STO scenario from ECC ?

thomas_schulze2
Active Participant
0 Kudos

Hello experts,

I'm seeking for some short infos around using / support of the "single document CrossCompany StockTransfer Order" process from ECC and whether this can be used within APO. If someone has some experience with this I would be happy to hear any feedback on this.

The starting point is that we use today an APO planning process for cross company replenishment via the famous 2-documents flow (IC PurchOrder --> IC SalesOrder) and we wanted to check if APO-SNP can support the simplified STO scenario. The "beauty" of course is that you only have a single document to deal with in an intercompany process.

  • Can SNP create STO PReqs (is this only depenend on the source-of-supply definition in the vendor master in ECC) ?
  • Can SNP Deployment process such SNP STO PReqs at a hub location ("fair share" at supplying plant)?
  • Can TLB by used at a Hub to turn such "deployed" STO PReqs into STO PurchOrders in ECC ?
  • Is the fcst consumption of such STOs working in the supplying plant side ?
  • Are there any serious / known limitations working with STO in APO (using Interchangeability, using GATP in the supplying plant side to perform rescheduling by BOP on these STOs etc.)

Thanks for any hints or experience sharing !

Regards

Thomas

Accepted Solutions (0)

Answers (1)

Answers (1)

frank_horlacher
Employee
Employee
0 Kudos

Hi Thomas,

you can check this with our

SAP Demand and Supply Network Planning rapid-deployment solution

http://scn.sap.com/rds-dpa

in combination with our

SAP Best Practices Baseline package

http://service.sap.com/bestpractices

contact me directly for more details.

Frank

thomas_schulze2
Active Participant
0 Kudos

Hi Frank,

I checked both of your sources given (RDS for DP/SNP) and the BP - Baseline. Unfortunately there was no specific info pointing to supporting the 1-document-CrossCompany-STO sceanrio.

What's the method to get contact with you on more details ?

Regards

Thomas

frank_horlacher
Employee
Employee
0 Kudos

Hi Thomas,

please have a look at

SAP BEST PRACTICES BASELINE PACKAGE - BUILDING BLOCKS

141: Internal Procurement: Cross-Company Stock Transfer

There you can see an example for your requirement.

In our

SAP BEST PRACTICES SAP DEMAND AND SUPPLY NETWORK
PLANNING RAPID-DEPLOYMENT SOLUTION

we do not cover the plant 1010 but you can easily get the process running with the RDS scope.

perform the following steps:

  1. Create integration model for plant 1010
  2. Integrate material H11 in plant 1010
  3. Integrate purchasing info record for H11 from 1000 to 1010
  4. Integrate transactional data for plant 1010
  5. Create means of transport for the transportation lane from 1000 to 1010
  6. maintain distribution definition for external procurement for plant 1010

After that you can execute the same process as described in the business process description

YPH: Heuristic-Based Supply Network Planning

or

YPO: Optimization-Based Supply Network Planning

the SNP algorithm will create the stock transfer purchase requisitions. Which you can covert to purchase orders.

I tested the example with material H11 and it worked fine.

TLB is not in scope of the RDS.

BR Frank

thomas_schulze2
Active Participant
0 Kudos

Hi Frank,

thanks for the detailed info - this helps to find a way thru the larger documentation. In regards to applying / testing the RDS we will check getting an SCM sandbox "on-hand".

Beside this I started searching OSS on my initial question - note 1284461 - Release Restrictions for SAP SCM 7.0 seems have some items to around using  "STO" in APO SNP & GATP (see below).

Another note explicitely defines how to get the right "SourceOfSupply" definition into APO for the STO sceanrio: 1623475

So, what is basically left open for me is:

* is TLB correctly working using "SNP Deployed STOs" ?

* at the supplying plant of the STO (typically a central DC) - is GATP able to catch at least demand of such STOs for ATP qty consideration

Regards

Thomas

***

Stock Transport Order and product interchangeability

The functionality of product interchangeability in Stock Transport Orders (STO)s

will not support

- purchasing requisitions and scheduling agreements

- old purchase transaction e.g. ME21

... 

.. the handling in case of inconsistencies between confirmed quantity in STO/delivery

and real quantity in warehouse at time of goods issue can only be resolved as

follows:

- Either deletion and recreation of STO and delivery

or

- post goods issue with #real# quantity (reduce delivered quantity), post goods receipt and

set delivery complete indicator, correct situation in warehouse, create new STO

item.

Backorder processing for Stock Transfer Orders - Rescheduling

The rescheduling for Stock Transfer Orders is done in LC during the update.

Rescheduling is supported during Backorder processing (BOP) but the results are

only consistent with LC scheduling if Configurable Process Scheduling (CPS) is

used.