S AP S D Aca de my I ns truc tor: Joe l G opfe rt

TSCM60 4.7 Part 1 Apostila 3 Shipping Logistics Execution Goods receipt process; Goods issue process; Internal warehouse process; Transportation process; The basis for the shipping activities, such as picking, packing and printing shipping documents, is the delivery document (outbound delivery). The Shipping Process (PROVA) SAP R/3 supports the following functions within shipping process: o o o o o o o o Monitoring the deadlines for reference documents due for shipping (ex. Sales and purchase orders); Creation and processing of outbound deliveries; Monitoring of goods availability; Monitoring of the capacity situation in the warehouse; Support of picking; Packing of the delivery; Printing and distribution of shipping documents; Processing of goods issue;

The deliveries in the shipping department that have already been posted for goods issue can form the basis for creating a work list for billing.

Structure of the Delivery Document The delivery document consists of a header and number of items; The data informed in the header are valid for the whole document, meaning that ship-to party. Shipping point, route and so on area unique for each outbound delivery;

Relationship between Order and Outbound Delivery Its possible to define in customer master record or customer material information that only one delivery is permitted per delivery document or that partial delivery is permitted as well; It is also possible to combine several orders to create one outbound delivery (collective process). Document Flow Status The overall processing status of the outbound delivery is in process until the billing document is generated, even if the shipping processing activities, including picking and goods issue, are complete. Difference between Outbound Delivery and Shipment Outbound delivery supports the processing of shipping activities in the warehouse and at the shipping point. Basically, each outbound delivery starts at a shipping point, continues along a route and has a ship-to party as a destination. Shipment if it is necessary to have several outbound delivery that are to be loaded onto a truck and the truck is to deliver goods to several shipping points and ship-to parties along a particular route, so it is necessary to have a transportation document called shipping document. Automatic Determination for Route Shipping point departure zone; Shipping condition; Transportation group; Transportation zone.

Organizational Structure: Logistics Client Company Code Plant assigned to only one company code. Storage Location where the stocks are managed.

Organizational Structure: Warehouse Warehouse Number Storage Type the different warehouse areas that differs with respect to their technical features. Picking Area

 Tips

Staging Area it is a part of the warehouse where goods are stored immediately after unloading or shortly before loading. Door it can be used for both inbound and outbound deliveries.

A warehouse number is assigned to a combination of plant and storage location. Several storage locations within a plant can refer to the same warehouse number. As a result, they form the warehouse complex from the point of view of Inventory Management.

Organizational Structure: Shipping Shipping Point it is directly under the client level. It controls the outbound deliveries and goods issue. An outbound delivery is processed from a single shipping point. The responsible shipping point is determined in the order at item level. Several shipping points can be assigned to one plant. A shipping point may also be set as goods receipt point, which means it can also be used for inbound deliveries. Controlling Deliveries The delivery types controls: o o o o o o o o Number assignment; Partner; Delivery split by warehouse number; Texts; Reference to order; Relevant for shipping; Route determination; Output.

Delivery Item Categories controls: o o o o o o o Check for over delivery; Picking location determination; Availability check; Check minimum delivery quantity; Automatic batch determination; Packing control; Relevant for picking.

Tips Required shipping criteria due to many deliveries are shipped together: Same shipping point; Same route; Same ship-to party.

Determining Item Categories in Deliveries Delivery type; Item category group; Usage. Shipping-relevant Customizing in Sales Delivery relevance in the order item category level is valid only for texts or value items; Physical deliveries (referring to stocks) are only possible if schedule lines are used; The goods movement type is defined at schedule line category level.

Shipping Point Determination (PROVA) The shipping point is determined for each order item; It depends on: o o o Plant; Shipping conditions; Loading group.

The shipping condition is proposed from the sales document type if a shipping condition has been assigned to it. If not, the shipping condition is proposed from the master record of the sold-to party.

Once is assigned, the shipping point cannot be changed in the outbound delivery.

Determining the Picking Location The picking location can be assigned in the order and them used in the delivery or directly in the delivery; The system determines the picking location based on a rule defined in the delivery type: o o MALA based on the shipping point, delivering plant and the storage location condition as defined in the material master; RETA and MARE these one are mainly used in trading scenarios.

The picking location search is activated for each delivery item category.

Picking Transfer order (full WM or Lean WM) is a document with which the goods movements within a warehouse complex can be initiated and monitored. Transfer orders include the material number, quantity to be moved and source and destination storage bin. WM x Lean WM Complete WM uses randomly organized warehouse (several and different storage bins at the same time); Lean WM uses fixed bin warehouse (a particular material is always in the same storage bin). Some of the WM functions not included in Lean WM are: o o o o o Storage sections; Reserve storage bins; Strategies for put away and picking; Replenishment; Inventory at storage bin level.

Creating and Printing Transfer Orders Creating o Printing o o o Tips Posting goods issue is only possible if the picking quantity and delivery quantity are the same. Only the pick quantity affects the picking status in an outbound delivery. When a transfer order is created, the system sets the delivery quantity as the picking quantity and the picking status is set to C (=fully picked). Special Functions for Processing Deliveries Single print one page for each TO item; Combined print one list for the entire transfer order; Pick list only for collective processing. One list for several orders. With reference to an outbound delivery, directly from the outbound or via transaction, collective processing.

Batches (Lotes) The flag that determines if a material is handled in batches is assigned in material master record in the Storage 1 and Purchasing screen. When delivering a sales order, this batch is copied to the outbound delivery and this information cannot be changed there. If the batch is not specified in the sales order, it is possible to inform one in the picking overview screen of the outbound delivery. The batch has to be informed before the goods issue is posted. The batch can be splited if the quantity of an item has to be taken from different batches. This can be done as follows: o o o o Manually in the batch split screen of the delivery item; Using the automatic batch determination when creating an outbound delivery (this function can be activated in the delivery item category); Through manually triggered batch determination in the batch split screen; In the Warehouse Management.

Serial Numbers A serial number can be assigned to each relevant material. This assignment can be done by entering serial number profiles in the material master record; The system can determine the serial numbers automatically. Usually the serial numbers for materials are specified in the delivery item. However, it is possible to define them in the sales order too. Pricing in the Outbound Delivery The outbound delivery can contain shipping-related conditions at header level (shipping or freight costs if the Transportation is not being used). These conditions can be informed in the delivery document manually or using the condition technique to determine it automatically. They can be printed in the delivery note or be transferred to the billing document, but it is not possible to transfer them from the preceding documents to the outbound delivery. Splitting an Existing Delivery An existing delivery can be splitted if it is necessary; When the delivery split is called (VLSP), it is necessary to inform a split profile that determines the parameters that will be used by the system to separate the quantities in different deliveries. These parameters are defined in Customizing and assigned to delivery types.

Delivery Interface: Communication Scenarios (PROVA) Based in the IDOC DELVRY02 (4.6A) and DELVRY03 (4.6B)

Log of Incomplete Items It is possible to call the log of incomplete items from delivery processing or select incomplete deliveries documents by selecting a special report; In the outbound delivery the system can check the incomplete data at both header and item level; In the incompletion log is possible to determine which fields are required to complete the document and what effect the missing data can have in subsequent documents (picking, packing, goods issue, and billing). In the same way, it is possible to define mandatory partner functions and texts and, if they are not informed, the system enters a note in the log of incomplete items. More Functions in the Outbound Delivery (PROVA) Material Substitution; Credit and risk management; Controllable error messages; Delivery split by warehouse number; Group of outbound deliveries; Dangerous goods check; Export control; Texts; Quantity checks.

Packaging Materials Specific material master data material type VERP or LEIH.

Handling Unit (Unidade Comercial) Individual packaging type.

Packing Functions Multilevel packing as many levels as required; The delivery item category relevant for packing is defined in customizing (packing allowed, packing not allowed and packing mandatory); The standard output types for packing are Packing List (at delivery level) and Shipping Label (at handling unit level). Packing in the Sales and Distribution Process

The packing function is available: In orders as packing proposals that can be copied to the outbound delivery; In outbound deliveries that can be copied to shipment documents; In the shipment document. The packing can be changed in the outbound delivery as long as the goods issue is not posted yet.

Proposed Packaging Materials (PROVA) It is possible to set allowed packaging materials for a material to be packed. In the material master record the field material group packaging materials have to be maintained. In the customizing, the packaging materials are proposed from the table allowed packaging material for each material group. If the field material group: packaging material has not been maintained in the material master, this material can be packed in any packaging material depending on the weight and volume check. Packaging Materials Types Item Category Group VERP: Billing for the packaging material; Item category determination DLN; These items can be copied to the billing document; Order Type Return LN, then subsequent billing.

Item Category Group LEIH: Returnable packaging processing; Item category determination TAL; These items are not copied to the billing document; When goods issue is posted, the materials are transferred to special stock for the customer; Order Type Return LA, then returns delivery RE.

Goods Issue Posting goods issue for an outbound delivery completes the shipping process; It can be posted by changing a single outbound delivery, use collective processing or it is possible to use the outbound delivery monitor to do this; Goods issue applies to the entire outbound delivery.

Effects of goods Issue Posting (PROVA) After the posting goods issue, no changes in quantities can be made in the outbound delivery document; It reduces warehouse stocks; Posts the value change to the stock accounts in inventory management; Reduces delivery requirements; Enters status information in the outbound delivery; Is stored in the document flow; Creates a work list for billing.

Canceling Goods Issue It is possible to select one or more outbound delivery for cancellation; Delivery number, shipping point, the route, goods issue date, group of outbound deliveries and shipment number are the selection criteria for the search of documents that will be canceled. Quality Management in Shipping If a quality inspection is to be carried out for the material, it is necessary that the quality management view in the material master be specified. It is possible to define if the quality inspection must be accepted before the goods issue or if the quality processing can be done paralleling to shipping. After the inspection, it is possible to print a quality certificate from the output control of the outbound delivery at item level. This function is common used for materials that are handled in batches. Proof of Delivery Pricing It is designed to support the process of creating the billing document only when the customer has confirmed the arrival of the goods; This confirmation is transferred by IDOC to SAP R/3 and confirms the entire delivery; If there are quantity discrepancy, the process have to be continued manually; The creation of the billing document is blocked until the proof of delivery has been confirmed; The proof of delivery function can be used after the decision of what item category is relevant for the POD process. It is also necessary that the reasons of deviation are informed in the customer master data.

Groups of Conditions: Pricing; Discounts/Surcharges; Freight; Taxes.

Condition Records Level on which the condition is defined; It is informed manually by the user and can be defined according to validity period, scales, depending on sales organization, etc. It is a master data (price list, discount list, freight list, tax list, etc.).

Condition Types It determines the category of a condition and how it is used (price, discount %, discount weight, etc.); Pricing Procedure All condition types permitted in pricing are contained in the pricing procedure; How the system uses the conditions and the sequence of access is determined in the pricing procedure. Access Sequence It is defined for each condition type in the pricing procedure, except for header and manual only condition types); Each access performed during the access sequence is made using a condition table;

Pricing Overview According to sales area, customer and document type one relevant pricing procedure is determined for each sales order type; The system reads the condition type for the first step and than determines the access sequence for this condition type; The system reads the access sequence and searches for valid condition records with the key specified by the condition table; If the first access does not find a valid condition record, the system searches in the next condition table until it finds the condition record that is valid for the data specified in the sales document;

This process is repeated for each condition type until the system has finished the entire pricing procedure.

Excluding Conditions Conditions can be linked to requirements in the pricing procedure; A requirement can evaluate the condition exclusion indicator and ignore the condition if set; The condition exclusion indicator can be set in either the condition type or the condition record; You may create your own exclusion indicators and test for their existence in the requirement routines. Changing Prices Manually in Documents In the condition records is possible to set limits for manual changes; The conditions can be entered in the sales document manually as well as automatically. They are marked if entered manually; It is possible to create or change condition in condition screen; It is possible to prevent manually changes in conditions by making the appropriate setting in customizing. Conditions in the Document Header The header conditions are valid for all items of a sales document; They are distributed among these items based on the net value of each one; The basis for distribution can be changed in the pricing procedure by selecting the appropriate routine in the AltCBV field (alternative formula for condition base value). Procedure determination selects correct pricing procedure; Pricing procedure defines how condition types are linked; Condition type represents properties of the pricing conditions; Access sequence contains hierarchy for condition record access; Condition table defines key fields of the condition records.

Special Condition Types HM00 allows you to enter the order value manually (?????); PN00 allows you to specify the net price for an item manually; AMIW and AMIZ minimum value for each order. It is a statistical condition; PMIN minimum price for a material. If the minimum price is not met during pricing, the system determines the difference using this condition type;

PR02 interval price. Condition records with interval scales have to be set with D in customizing; HI01 hierarchy discount; KP00 pallet discount; KP01 Incomplete pallet surcharge the customer pays a surcharge for an incomplete pallet; KP02 Mixed pallet discount accumulates the quantities of the individual items, then calculates the discounts for complete pallets only; KP03 Surcharge for incomplete mixed pallets; Rounding DIFF difference amount (arredondamento). Condition type DIFF is a group condition.

Statistical Condition Types VPRS is used to retrieve the standard cost of the material. It is a statistical value in the pricing procedure. Using condition category G, the condition accesses the material value standard or the moving average cost in the material master date. Using condition category S, the condition will only access the standard cost. And using condition category T, only the moving average cost. SKTO cash discount rate. Condition category E. EDI1/EDI2 Customer expected prices.

Tax Determination Criteria Departure country country of the delivering plant; Destination country country of the ship-to party; Customer tax classification; Material tax classification.

It is possible to assign a rule, that can be BLANK, A or B, at the sales organization level to determine the sales tax classification number in the order and billing document. For the status BLANK, the standard system does as follows: o o o If PY has a sales tax ID and a different SP The tax number and tax classification are taken from PY; The tax number is determined according to the tax destination country.

If the item above does not apply: o If the SH has a sales tax ID or the SP has NO sales tax ID, the tax number and tax classification are taken from the SH.

If the item above does not apply:

Tax number and tax classification are transferred from the sold-to party.

With status A, the tax number and tax classification are generally transferred from the sold-to party. With status B, data is transferred from the payer in the same way as rule A.

Tax Determination Business transaction (domestic or import/export); Tax liability of the ship-to party; Tax liability of the material.

Pricing Procedure for Taxes Condition technique; Condition type MWST; Access sequence MWST.

Tax Interfaces (USA) (PROVA) TAXUS (taxes are calculated in SD); TAXUSJ (taxes are calculated in the central tax procedures using the tax jurisdiction stored in the master data of ship-to party); TAXUSX (taxes are calculated via a RFC and a central tax procedure).

Agreements Define promotion or marketing plan for a product line for a certain period of time; The promotion is linked to specific sales deals that are linked to special condition records;

Release Status for Sales Deals _ = released; A = blocked; B = release for price simulation; C = release for price simulation and planning.

Rebates (Bonus) They are based on the sales volume generated by the customer within a specified period and are paid retrospectively; When the rebate relevant billing documents are processed, accruals can be determined and posted automatically. The rebate credit memo then reverses these accruals, if desired.

Prerequisites for Rebate Processing (X) Rebate active - Sales Organization; Payer master record; Billing document type. Creating Rebate Agreements Creation of rebate agreement with a specific rebate agreement type; Condition records are linked to the rebate agreement specifying the rebate and accrual rate; Creation of relevant-billing documents; Creation of credit memo request for the rebate payment amount specified.

Rebate Type Agreements Material rebate Customer rebate (condition type BO03) Customer hierarchy rebate (condition type BO04 and BO05); Material group rebate Independent of sales volume (condition type BO06).