SCM TransportationLanesandQuotations 200519 0513 23004
SCM TransportationLanesandQuotations 200519 0513 23004
Purpose:
This site is providing information about SCM Transportation Lanes, Quota Arrangements and related object such as Source of Supply, External
Procurement Relationships.
Overview
Table of content:
Transportation Lanes
Transportation Lane Maintenance
Database Tables
Consistency check programs
FAQs
Quota Arrangements
Related contents
Transportation Lanes
Online SAP Help Documentation Link
Transportation lanes are business objects that generally include a starting (from) and a destination (to) location (in special case of External
Procurement Relationsip, F&R, there is only an end location) and assigned to a Model. There is a product transfer taking place on the
Transportation Lanes. It can happen to All Products or to defined products: only for 1 product, product groups, or a selection of products.
Based on the T-lane date validity concept the validity dates of Product Specific Transportation Lanes with the same product number must
not overlap, if the lock indicator is ''Available'' or ''Locked'', only in justified cases. Otherwise an error message is displayed. The lock
indicator (SPRKZ) set for ''Flagged for Deletion'' can take out the lane from validity check.
Justified cases: There are specific factors in between the properties of the T-lane which can distinguish T-lanes with the same Product
and overlapping validity from each other. For example if ''Indicator for Subcontracting'' , ''Source of Supply Category. (Contract, Sched.
Agmt, Info Record)'' are different for two products, they can overlap in their validity (no error is shown).
Respective error message: Message no. /SAPAPO/OO_TR114 (or in case of post-check, when the entries are already created:
/SAPAPO/OO_TR224)
Code part for validity overlap: (SE38) - /SAPAPO/SAPLOO_TR_TLANE_MAINT > /SAPAPO/LOO_TR_TLANE_MAINTI06 >
CHECK_SPRKZ_0121
In the above code lines one can read out, which factors are able to distinguish t-lanes for validity overlap check.
You can check if there are overlapping product specific transportation lane entries in your system with the report provided in the SAP Note:
2011126 - Report for checking overlapping Transportation Lanes
You can check your Transportation Lane's consistency from several aspects by clicking on the icon illustrated below in the transaction
/SAPAPO/SCC_TL1:
For this reason you can set up different consistency check flags to decide whether the check process can ignore them or take them as an
error message. This panel is available from transaction: /SAPAPO/SCC_TL1 > Settings / Settings (at the Menu bar). These settings are
user specific.
This can be particularly useful for example in the case described in SAP KBA: 1841761 - Transportation lanes are created even though
Products/locations do not exist
You can define values into the version dependent fields of a product specific transportation lane. You can choose the planning version on
the initial screen of /sapapo/scc_tl1. In this case only the version dependent fields are eligible to edit, the version independent fields are
greyed out.
Geocoding IGS Tool for Transportation Duration and Distance calculation in Transportation Management / SCM systems
For automatic Means of Transport creation via CIF please make sure the following customizing path setting is enabled: SPRO > APO >
Master Data > Transportation Lane > Maintain Means of Transport. The field is 'Creat. CIF'. This requires product group settings, please
see F1 help on this checkbox for details.
In case of an APO system the TSP is a Location object (Type 1020). Transaction to display is /n/sapapo/scc_tl5 or /n/sapapo/scc_tl1.
In case of a TM (Transportation Management) system it is a Business Partner. Transaction to display is /n/scmtms/tl5. To make a
business partner eligible for carrier selection on the T-lane the BP must exist with the Role = Carrier (CRM010 code) in the database
table: BUT100. Use transaction BP to adjust the role to carrier. If the BP is created from ERP, use the CIF to create the carrier role for the
business partner. See SAP Note: 1437320 - Business Partner role "Carrier" not created
Create Transportation Lanes using the Core Interface Function from ERP
The following BAPIs can be used as they are released for customer coding to read/change/create/delete of transportation lanes:
Database Tables:
You can find the tables in SE11 or SE16 transaction by typing /SAPAPO/TR* and press F4 help. This will list the Transportation Lane related
tables.
ZZTRPRODM_VALIDITY_ADJUST_ALL (1457417) - For this note the version 5 is the latest (make sure your system includes the latest
version of this note, please check note validity section in the note for details, the Z-report inside the note is release-independent).
Z_TRPROD_TPSRC_VAL_CORR ( 2024461
2024461 - Error messages during MASSD transportation lane update
Z_TR_OVERLAP - 1935946 - Overlapping validity or duplicate transportation lanes (error messages during transportation lane update with
MASSD) > returns numbers based on TRPROD > correction to be made manually
1111666 - Inconsistencies in /SAPAPO/TRPROD and /SAPAPO/TR > this report inserts missing entries into TR < (same as manually create the
T-lane in /SAPAPO/SCC_TL1 for which no //TR but only //TRPROD entries exist)
2011126 - Report for checking overlapping Transportation Lanes - returns TRPROD IDs > correction to be made manually
1530708 - Corr. report for inconsistencies between //TPSRC & //TRPROD (Checks if the BZQID entry from //TPSRC exists in //TRPROD)
This function is however not in standard system by default. By default you get a message when trying to use the transaction: "Process. w. stock
transp. requisitions is not supported in standard sys."
Implement the enhancement spot '/SAPAPO/ENH_MRPAREA' from transaction (SE18) to use the function based on the note: 1402298 -
Purchase order handling release with MRP areas.
EXPORTING
IV_GLOBAL_CUSTOMIZING = 'X'.
It is important to activate all objects after the BAdi implementation to make the implementation called. The transaction screen of
/N/SAPAPO/MRPACUST01 looks like below afterwards:
About the effects of the flag in the system you can find information in the note 2094078 - Stock transfer document settings on T-lanes which
explains the documentation with a ''matrix'' view that you can already find in the F1 help in the /SAPAPO/MRPACUST01 transaction.
SAP note: '' 1516112 - Authority check for transportation lane maintenance apps'' provides with the implementation of the function for APO
administrators to set up the authorization concept for Transportation Lanes. If the SP release of your system is higher, then the note's validity,
then the code parts and the function is already in your system.
You can use the standard implementation or create a new one tailored to your business requirements. Here the authorization can be widely
customized.
The method is called by Function Module (SE37): /SAPAPO/MD_CHECK_AUTHORITY ( CALL METHOD gr_badi_check_auth->first_authority_
check )
For /SAPAPO/SCC_TQ1 transaction the following note is necessary to be implemented prior otherwise the BADI cannot be applied:
FAQs:
Q: Why are the Valid from and Valid to dates fields are greyed out in a Product-Specific Transportation Lane causing that I cannot edit/change
them?
A: The greyed out validity date fields are due to the transaction design. Validity overlapping is not allowed for the same product on the T-lane.
This overlapping is checked during the Product-specific t-lane creation and not during change mode. One possibility to change validity is to delete
and recreate Prod-spec T-lanes with the new dates.
Note: There are parameters that make the Prod.-spec. T-lane entry unique. Eg. Subcontracting flag allows validity time interval overlap if it is set
on the one product and not set on another product with the same no.
Quota Arrangements:
FAQs:
Q: Why is Start Date not definable in some releases in Quota Arrangement?
A: KBA Note: 1698146 - Quota Arrangement field "Start Date" cannot be maintained in APO. Example: if we have a header for product xyz from
04/24/2013 to 06/30/2013 and we create another header for the same product with end date 06/15/2013 then the first record end date will be
modified to 06/15/2013 and second record record start date changes to 06/16/2013 with end date 06/30/2013.
A: There is only a very limited authorization concept existing for Quotations. It is only checked if a user has the authorization for the concerned
model. There is no possibility to distinguish based on locations. Quota Arrangement transactions are not that simple when we look from the
location's aspect. If you are entering to a location inbound or outbound quota, there are possibilities to add partner locations as well. Therefore a
location based check would make the whole concept unimaginably complex so it is not surprising that this functionality is not available.
Recommendation is to sort the user authorizations based on activity type (display and change) and plan the business line accordingly.
For CIF transfer related error messages, that are not detailed in the SMQ2 transaction, you can search in transaction SLG1 with the object:
''CIFSCM''
Related contents:
Guided Answers for BAPI_TRLSRVAPS_SAVEMULTI2
Understanding rounding and conversion in Transportation Lane duration, costs and distance
Create Transportation Lanes using the Core Interface Function from ERP