Route determination steps

Hi,
I am in the learning process and would like to read some simple documents on step by step procedure for configuring route and to define Route determination.
Does anyboy have some good documents on Route determination?
Thanks in advance.
Cheers
VJ
[email protected]

One important thing that Jean missed out which also plays a part in Route determination:
"Shipping condition defined in shipping point determination. "
If a shipping condition has been assigned to a sales document type this condition will be proposed in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party.
Also, remember that SAP copies the route from the sales document item into the delivery at header level.
In case you do not have a sales document item that you are referencing ( Like in a subcontract delivery), then you need to define weight groups as well.

Similar Messages

Condition check (based on sender file name) at receiver determination step

Hi,
My scenario is File to AS2 (Sender side file adapter and receiver side AS2 adapter)
We have 5 customers, but the source location is same to pick the files, Here we are not using any ESR objects.
Based on the source file name PI need to determine to whoom this file need to send at receiver determination step
Craeted objects
1 Sender CC,
1 Sender agreement,
1 Receiver determination
5 Interface determinations
5 Receiver agreements
5 Receiver CCs.
Could you please provide me your valuable inputs.
Thanks
Ramesh

Hi Venkataramesh,
I understand your scenario as, picking files (different file naming standard for different target customer) from one source folder. Based on file name, that payload should be sent to corresponding target customer. You have mentioned u201CHere we are not using any ESR objectsu201D. I can see two reasons for this decision
1. PI is used to route the messages, i.e., no need to transform the payload. OR
2. Files can binary files like PDF, ZIP, JPG, GIFu2026
Now I can see two possible solutions
1.     Simple solution, as proposed by u201CPrabhu Rajesh Janardananu201D, make it into 5 different scenarios (5 sender channels).
2.     Bit complex solution, only one sender channel, using extended receiver determination
Step 1:- In Sender File channel check u201CAdapter u2013 Specific Message Adapteru201D in Advanced tab. File Name should be checked.
Step 2:- In Receiver Determination, Select Type of Receiver Determination as u201CExtendedu201D. http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a423a8e5430e10000000a42189b/frameset.htm
Step 3:- Do a Graphical Mapping (use it Operation Mapping in Receiver Determination).
Step 4:-
Source and target of graphical mapping will be same (below), because you donu2019t want to access input payload (it can be XML, flat file, JGP, GIF and you donu2019t have its structure).
<Receivers>
   <Receiver>
      <Party agency="" scheme=""></Party>
      <Service></Service>
   </Receiver>
</Receivers>
Step 5:- Write a UDF in Graphical mapping as below. http://help.sap.com/saphelp_nwpi71/helpdata/EN/43/03612cdecc6e76e10000000a422035/frameset.htm Pay attention to method declaration
public String Determine_Receiver( Container container) throws StreamTransformationException
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(u201Chttp://sap.com/xi/XI/System/Fileu201D,u201CFileNameu201D);
String valueOld = conf.get(key);
//Put your logic here
if (valueOld.equal(u201Cuser1u201D)) {
return u201Cuser1u201D;}
if (valueOld.equal(u201Cuser2u201D)) {
return u201Cuser2u201D;}
if (valueOld.equal(u201Cuser3u201D)) {
return u201Cuser3u201D;}
Step 6: Now use this UDF to map to u201CReceiveru201D and u201C Serviceu201D.
This solution need more fine tuning.
Regards,
Raghu_Vamsee
Edited by: Raghu Vamsee on Jan 8, 2011 5:56 PM

How does Receiver Determination Step in BPM work?

Hi,
I'm still in trouble with the Receiver determination step in the BPM...
Normally, when you use the send step, it sends the message in the flow context. Am I right, when I suppose, that when you put the receiver determination step before this send step, the send step sends the message in the context of the receiver determination - that means: if in the Integration Directory, there is receiver determination (with some conditions) and these are matched with the message in the send step, the send step sends it into the receiver, that is defined for the condition and not in the flow context... Right?
Please, write me just your experiences and not links to the documentation. I read it all, but... :O(
Thanx 4 your help, Peter

Hi Peter,
The receiver determination step is used to get a list of receivers for a subsequent send step.It makes a call to the receiver determination you configured in the Integration Directory and returns the receiver list.
Here you specify the send context and the multiline container element for the receiver list.
The send context is a string.The send context can have any string value and depending upon the condition in recvr determination you can route to multiple receivers.
Regards
Priyanka

Route determination for PO and Delivery

Hi Experts,
I would like to ask how to set up route fro deliveries and Stock transport orders.
Hope you can help me on this.
Thank you very much.
Regards,
Mylene

Working with Route Schedules
Use
Using a route schedule, you can control periodic customer deliveries of a particular shipping point to different ship-to parties (for example, customers or stores) in a certain sequence on a certain defined route. The planning is based on calendar weeks. The period unit is a day. Also, route schedules have a goods issue time.
The route schedule function supports the following processes:
Periodic deliveries from a shipping point to stores or customers are planned in advance on the basis of calendar weeks and weekdays, also without reference to particular deliveries.
You adapt the schedules in the specific cases to the planning. For example, you can plan a GI date for a Monday at 8 oclock, without knowing the exact date or the delivery.
On the basis of this planning, deliveries that are to leave the warehouse at the same time are combined into groups. In Shipping you can thus distribute the workload by processing these groups.
Features
You can display all deliveries for a particular route schedule on a particular day, for a particular shipping point, and so on. In this way, for example, you can choose picking lists on the basis of route schedules.
You can create route schedules for the following documents:
Sales orders
Stock transfer orders
Deliveries that are based on sales orders, store orders, stock allocations, stock transfer orders, and deliveries without reference.
The route schedule is displayed in the header data of the delivery. For each delivery within the route, the system prints the expected date and the expected time of the delivery (on the basis of the local time at the original shipping point) on the delivery note; the goods issue date is used for the goods issue posting and the stock valuation.
In Customizing, you define for each shipping point, delivery type, stock transfer order, and order type whether or not route schedules are to be used.
You create the route schedules in the master data for shipping. Here you define the route schedule determination and the validity period for the route schedule and the itinerary.
As soon as the legs have been defined, you can branch to another screen to determine the actual itinerary, as well as the time (days/hours/minutes) required to get from one unloading point to the next. In this screen there is a field beside each leg. Here you can enter the number of the itinerary for the individual legs of the route. If, for example, you enter legs A and B, but assign itinerary number 2 and 1 to these, B is the first unloading point on this route. If you press Enter, the legs are displayed in the correct sequence.
At the same time it is possible to control the route schedule determination for each delivery type, stock transfer order, and order type. It is activated in the same manner as the repeated route determination. If the route schedule determination for a delivery is active, the system automatically attempts, during creation or change of a delivery, to determine a route schedule and records this in the delivery. Simultaneously, the scheduling is adjusted. All the deadlines, for example, the transportation planning time, the picking time, the loading time, the goods issue time, and the delivery time can change.
Deliveries with the same route schedule and the same date can be selected for the same picking run and the same goods issue. The same procedure can be used for printing delivery notes and freight lists, for the grouping of deliveries into shipments, and for confirmation of picking orders.
Deliveries that leave the warehouse at the same time, but are assigned to different routes and can therefore have different route schedules, can be combined together and processed through the creation of wave picks. The only condition is that all deliveries have the same goods issue time.
Route Schedule Determination
If exactly one route schedule is defined for a particular combination of requirements, then the system will use this.
For each combination of requirements for the route schedule determination, you can define several route schedules.
In the case of a delivery without a preceding document, the system determines the route schedule with the earliest delivery time at the ship-to party.
In the case of deliveries based on preceding documents (for example, stock transfer orders), the system searches for the route schedule that is nearest to the planned date/time of the delivery. The system uses the following search algorithm:
- If a route schedule exists for the specified time, this is assigned to the delivery.
- If there is no route schedule for the time specified, the system searches for the previous route schedule up to the GI time.
- If there is no route schedule from the GI time to the planned time, the system searches for the next route schedule in the future and assigns this to the delivery.
Requirements for Route Schedules
The route schedules are determined by the following conditions:
· Shipping point
Where are the goods coming from?
Ship-to party and unloading point
Where are the goods going to?
Shipping condition
How are the goods being shipped?
Transportation group
Which goods are shipped?
® For example, which type of goods?
Calendar week / year
When are the goods to be shipped?
If you do not explicitly enter the week and the year, the entry applies for each calendar week. If you enter a week and a year, the route schedule only applies for this week.
You can only use route schedules if you have maintained the working times and therefore at least one of the following times in minutes:
· Transportation planning time
· Pick/pack time
· Loading time
· Transit time
A route schedule can leave the warehouse exactly once in a week. If a route schedule runs several times, either on several days or several times a day, it must be copied to another route schedule.
Special schedules and public holiday weeks are possible.
Processing a Route Schedule
Implementation Options
Wholesale trade customers and stores can receive goods at regular intervals. These delivery rhythms have an influence on the workload in the warehouse. To help delivery planning, the route schedule serves as a tool for planning regular, repetitive customer deliveries on a particular route. At the time of planning, potential deliveries that have not yet been created are grouped in the route schedule. When the deliveries are created, the system can automatically determine a route schedule and assign it to the delivery. All deliveries with the same route schedule and the same date can be processed together in the shipping point. All these deliveries leave the shipping point together at a particular time. They are distributed along the same geographical route.
· Deliveries for route schedule MO10H leave the shipping on Mondays at 10:00 in the direction of Philadelphia.
· Deliveries for route schedule MO10M leave the shipping point on Mondays at 10:00 in the direction of Boston.
· Deliveries for route schedule MO10S leave the shipping point on Mondays at 10:00 in the direction of New York.
You can print picking lists for all deliveries that belong to route schedules MO10H - MO10S together.
Prerequisites
If you want to define route schedules, you must perform the following tasks:
- Activate the route determination
- Activate the delivery scheduling
- Activate the route schedule for your shipping point and make the following settings:
Transaction
Activity
Delivery
Route schedule determination for delivery type
Sales order
Route schedule determination for sales document type
Stock transfer order
Route schedule determination for delivery type
Set delivering plant and order type
Maintenance of the itinerary should be uniform for all the route schedules used. To ensure exact planning, maintain the itinerary for all the route schedules. If rough planning is sufficient in this case, you do not need to maintain the itinerary for a route schedule.
If you do not define any goods accepted times in the customer master for the unloading points of the ship-to party, the system assumes that the goods acceptance is possible at any time. The system determines the delivery time from the departure time in the route schedule plus the required traveling time to the ship-to party, as set in the itinerary (specific move time). This delivery time must be within the goods acceptance time of the unloading point of the ship-to party. If not, the respective route schedule is not determined during delivery creation.
For more information on route schedules, refer to the Implementation Guide (IMG) under Route Schedules.
Process Flow
Select the shipping point you are working for and enter the number of the route schedule.
Enter the data that defines the route schedule more exactly:
- Description of the route schedule
- Route
- Departure day (weekday)
- Departure time
You define the route schedule determination. When you create the delivery, the system can determine a route schedule on the basis of the following data:
- Shipping point
- Ship-to party
- Unloading point (if available)
- Shipping condition
- Transportation group
- (Optional) year/period
You enter this data (with the exception of the shipping point already entered in step 1).
You decide whether or not you wish to define the itinerary for this route schedule.
(Optional) You enter the itinerary and, if required, also the travelling time.
Creating a Route Schedule
Choose Logistics ® Logistics Execution ® Master data ® Transportation ® Routes ® Route schedule ® Create.
In the screen Create Route Schedule: Initial Screen, enter the shipping point and the number of the route schedule.
If you wish to use data from an existing route schedule as a reference, enter the respective shipping point and the number of that route schedule. If you also wish to copy the itinerary, check the Copy itinerary box.
Press ENTER .
The Create Route Schedule screen appears (here the system displays the number you just entered for the route schedule and the shipping point).
Enter the following data:
Description of the route schedule
The respective route
Departure day (weekday)
Departure time
In the Determine route schedule section, enter the following data:
Ship-to party
Unloading point (if available)
Shipping conditions
Transportation group
(Optional) Year/period
If you wish to define for this route schedule the itinerary according to which the individual ship-to parties are to be delivered to, choose Extras ® Itinerary.
The Create Itinerary screen appears.
Enter the itinerary and, if necessary, the travelling time.
When you determine the travelling time from one ship-to party to the next, you should include the wait time of the vehicle at the previous ship-to party.
If the same route is planned for several route schedules, define for each of these route schedules the same itinerary that should correspond to the stages and legs of the route.
Choose Goto ® Back.
You return to the Create Route Schedule screen.
In this screen, the Itinerary maintained field is now selected. If you wish to add other ship-to parties, you must also maintain the Itinerary for them.
Check your data and save your entries.
Reward if helpful...
Regards,
Diogo

Route Determination on Distance

Hi Gurus,
I want to determine the route on distance based i.e route should be determine on nearest distance i.e Kilometer based. Can we add Distance as creteria for route determination.
Thanks in advance.
Regards
Mahi

I dont think it is possible to determine route basing on distance. Bcs route determination is done basing on shipping point,destination zone, transportation group n shipping condition , wieght group (optional). But u can maintain unit of measure distance as kilometers in
Img- le- shipping- basic shipping functions- routes- define routes
-define routes and stages (step)

Route determination

Hai All,
In the step of define routes and sdtages, there is a field for procedure. If we give the standrad procedure how it will be effected in the route determination
2. Also we are checking the box cal;led shipping costs relevent. How we wll maintan the shipping costs
3. what is shiping type procedure group which we will find aat the define shipping types
Regards,
Keyur

Hi Keyur,
The shipment type procedure group is used for determining the pricing procedure for the shipment cost calculation.this comes into picture when the business processing is using the shipment and transportation in which the route place a vitol role.
As said above to get the Shipment cost calculation is a differnt issue for which lot of configurations has to take place like, Transporation Planning Point,Shiping type,shipment cost condition types and pricing procedures etc.,
Hope this clear your doubts.please reward if really helpful,
Thanks and Regards,
Sateesh.Kandula

Why does PI pickup wrong interface, in the interface determination step

I configured a scenario in id.
In ID, i can see the following when i open the interface determintation that i created.
Sender Details:
Communication Component:Sys_Sample_One_D
Interface: UserMasterQuery_Outb
Namespace: urn:sample.com:I_Legacy_JDBC_Application
Receiver Details:
Communication Component:Sys_Sample_Two_D
Interface:EmployeeEmailProcessing_Inb
Namespace:urn:sample.com:I_Legacy_FileApplication
Interface Mapping: UserMasterResultset_to_EmployeeEmail
But when i execute the scenario, and when i see in the the Interface determination pipeline step in moni, it is showing:
<SAP:Main..
     <SAP:Sender>
          <SAP:Service>Sys_Sample_One_D</SAP:Service>
          <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
     </SAP:Sender>
     <SAP:Receiver>
          <SAP:Party agency="" scheme=""/>
          <SAP:Service>Sys_Sample_Two_D</SAP:Service>
          <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
          <SAP:Mapping notRequired="Y"/>
     </SAP:Receiver>
     <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
In the <SAP:Receiver> section, the <SAP:Service>Sys_Sample_Two_D</SAP:Service> is as per my configuratioin,
but <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface> is not the interface that i configured as the receiver interface, infact this is the sender interface.
the correct receiver interface to be pickedup is EmployeeEmailProcessing_Inb
and finally it is showing the error in moni, in the Technical Routing pipeline step
<SAP:AdditionalText>No standard agreement found for , Sys_Sample_One_D, , Sys_Sample_Two_D,
urn:sample.com:I_Legacy_JDBC_Application, UserMasterQuery_Outb</SAP:AdditionalText>
the error i can see later, but i would like the right interface to be determined by PI,
i refreshed various caches etc, recreated the config objects in ID, but it is not picking up the right receiver interface.
any inputs appreciated, to find out what went wrong.
thanks,
Madhu.

Two threads which has some discussion regarding this happening in PI 7.1.Hope it gives you some help.
Incorrect Receiver Determination
Reciver Problem
And, as you have checked your Interface determination similarly can you also check your receiver determination.
Does the receiver determination have the correct receiver at the bottom ?

Receiver determination step in the BPM and multiline container

i have made a file2file scenario where:
there is a BPM,
the BPM has a send step which contains a receive step,
a transformation that mapps the incomin message to two messages(Split-messgae case),
and then a FORK step which sends the two messges to through 2 SEND steps to the intended receiver services.
It didnt work......and i followed a blog-> /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure ............... which suggested to have a
"receiver-determination" step in the BPM before the SEND step.... it says that this
"receiver-determination" step will put the message in a MULTILINE container..
i m confused bout this step ........ can anybody explain.....
please help

HI,
In receiver determination step selctthe multi line container element.in container editor create the one element with type as receiver and select the check box.
A Receiver Determination step returns set of receivers configured for the output abs interfaces in the directory and puts it into receiver which is a multiline container receiver element
Regards
Chilla

ATP and Route Determination at Storage Location Level

Hi Experts,
I'm working on a project currently and one of the requirements is to have ATP and Route Determination at Storage Location level. I know SAP standard for this is at plant level but was wondering if anyone has had this requirement before, and if so what course of action they took to solve this issue.
Any help would be greatly appreciated.
Thanks,
Mark

Hi Mark,
in my previous project we have a customized table created for all the route determination and used mv45afzz move field to vbap to determined the route.
not sure if there is a easier solution but at least it is doable through customization for sure.

Integration Process Receiver Determination Step

Hi experts,
May I know whether the "Receiver Determination Step" (in Integration Process) that collects the list of receivers configured, can be used only to find list of asynchronous receivers?
Can't we use this "Receiver Determination Step" in synchronous scenario? If yes, may i know how to?
Thank you!
Best Regards,
Saravanan

Thank you Gaurav!
I can understand we can use multi-casting.
To clearly put my scenario, I have to use synchronous send (so cannot split send and receive step, and so no need of correlation) in my BPM, which have to synchronously send (and so it receives within same step) message to multiple receivers. This is the reason I am trying to use receiver determination step first and in a loop trying to synchronously send message to each receiver and receiving response.
Now my problem is in the receiver determination step, it is not identifying any of the receivers configured in the integration directory. The receiver determination list returns empty.
So, I want to know whether this receiver determination step is only for async receivers or synchronous receivers also.
Best Regards,
Saravanan N

About receiver determination step.

how does the receiver determination step in bpm knows to calls which receiver determination in ID?
which parameter determines this?

>> is there receiver determination info in your header info?
the receiver for a particular msg is always determined from the sebder info in a msg : sender service, interface.namespace.
>>where to view header info?
u can see the msg in various stages at it passes thru integration engine in SXMB_MONI. u can see various pipeline steps...and see the msg as it leaves each pipeline step.
>>where do we should view the content of variables?
to monitor ur process and each step of it go to worklog's tech view and look for each step u want to monitor in detail .
regards,
latika.
[dont forget to mark helpful answers]

Receiver determination step - Send context

Hi Experts,
I have understood from SAP library and others threads that send context in the receiver determination step is used to send value for the conditions we have added in ther receiver determination and fetch only receivers those satisfy the cretiria.
Please validate whether my understand is right or not?
If its correct, then my question is can we populate this value dyanmically, say field value from another message.
Please clarify.
Thanks,
Kar

Check if the below link is of any interest to you:
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
From the link:
Condition: when the AirlineID field in the message payload has the value LH, then the message is
forwarded to the receiver business system BUS_100. A context object of the same name from the ES
Repository is used to access the AirlineID field in the message.
It talks about normal receiver determination as against the receiver determination step (of BPM) which you want....

BPM : Receiver Determination Step

Hi,
I was wondering why we need a Reciever determination step since on send step xi automatically find that there are multiple receiver and sends them accordingly to the different system as per reciever agreement.
Is it that the receiver determination is only useful for multicast which is for send and waiting for the message response from those receiver.
Kindly let me know your comments.
THnks

Hello chinna,
You need receiver determination step becoz even though in BPM u define what are ur receivers but not what service its handling. Lets say this is the scenario :
File>RFC>FILE
ex: /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
You dont specify in the receivers of BPM where to write the file and how to write the file?
Please elaborate ur scenario i coudlnt get the second part?
Vara
[PLEASE REWARD FOR POSTING]

BPM - Do we need receiver determination step between trans and sync send?

Hi Gurus,
I have a 1:1 transformation step followed by a sync send step. The transformation step is executing fine. While the sync step is executing, I am getting an error says 'No receiver determination found'.
While I am executing this sync step in a separate, it is working fine.
Do I need to have 'Receiver determination step' between Transformation step and Sync send step? I think so. Can somebody confirms this?
Thanks for your kind help.
Kalyan

Hi,
I think there is no need of a Receiver determination step in the BPM.
You should have a proper receiver determination in configuration for this BPM scenario. (i.e) A receiver determination from BPM to the service configured for the synchronous interface.
Regards,
P.Venkat

Receiver Determination Step For Synchrnous Send in BPM

Hi,
How to use BPM Receiver Determination step for a synchronous send step?
My scenario is to send a request to multiple receivers synchronously and get the response.How can i achieve this using Receiver Determination step in BPM.
Regards
Divia

Hi Sreedivia,
As far as use of synchronous message is concern with receiver determination step, it wont allow you to use Abstract Synchronous message interface in it.
Even you cannot give multiple receivers without specifying any condition while creating Receiver determination in integration directory.
Regards,
Sami.

Route determination steps

Similar Messages

Maybe you are looking for