SHIPPING POINT IN SAP

Shipping points are independent organizational entities within which processing and monitoring of the deliveries as well as goods issue is carried out. A delivery is processed by one shipping point only.

Path :

spro – enterprise structure – defining – logistic execution – define copy delete check shipping point

Click on image activity

Double click on define shipping point

Select the standard 1000 and copy

Create as you required

Assign factory calendar:

Loading time in days:

                It is a time taken to load the goods in to truck this field will help to perform delivery schedule in sales document

Pick/Pack time:

                It is a time taken to pick the material from storage location and to pack it this field will be use to perform delivery scheduling in sales document

The address text:

                It will help to determine the address of shipping point and to print it in relevant output.

Shipping point will determine in to sales document based on

1.       Plant

2.       Loading group

3.       Shipping condition  

Click here to watch how to create shipping point

SHIPPING POINT

STO RETURN PROCESS IN SAP

                                STO Return process in SAP

Return the goods from receiving plant to supplying plant

Process:
     1st step : create return purchase order. we have to check returns
     2nd step: we will create return delivery without

     3rd step: we will do MIGO
     4th step : after MIGO we will do PGR

Configuration for Return STO:

    Path:  SPRO - Material Management - Purchasing - Purchase order - Return order - Store return - Return plant to Plant

Go to combination of purchase order type UB and supplying plant and for this combination assigbn delivery type NLR.


                   STO Returns Purchase Order type: UB

                   STO Returns Delivery type: NLR

                   STO Returns Item category : NLRN

                   STO Returns Schedule line category: NR

                   Movement type two step process : 671

                   movement type one step process : 677


  In return STO when we do MIGO system determine movement type as 161 

• 161 movement type it reduce the stock from receiving plant 

• when we do PGR the stock will be updated in supplying plant 
• here the data will copy from Purchase Order to Delivery with help of copy controls between DL to NL.

INTER COMPANY STOCK TRANSPORT ORDER IN SAP

Intercompany stock transfer order in SAP SD

It is a process of transferring the stock from one plant to another plant.  That is from

                Manufacturing plant       to            Manufacturing plant

                Manufacturing plant       to           depot

                Depot                   to            depot

                Depot                  to            manufacturing plant

One step process:

1. PO (ME21N)

2. Delivery (VL10D)

3. Proforma invoice (VF01)

Two step process:

1.       PO (ME21N)

2.       Delivery (VL10D)

3.       Proforma invoice (VF01)

4.       MIGO (MMIGO)

In sto process the Purchase order type= UB

Delivery Type =NB

Item category = NLN

Schedule line category = NN

Movement type two step = 641

Movement type one step process = 647 

          

      The effect of 641 movement type:

1.       It reduce the stock from supplying plant and display the stock  in stock in transit in receiving plant

2.         Inventory accounting document generate. Accounting entry is

Stock out word movement CR TO

Stock in word movement Dr

The effect of movement type 647 (One - Step)

1.       It reduces the stock from supplying plant and in update the stock in receiving plant.

2.       It generate inventory account document the accounting entry is

Stock out word movement CR TO

Stock in word movement DR

In STO process while creating delivery with reference to purchase order how system is copying the data from purchase order to delivery that is we have copy controls from purchase order to delivery DL to NL.

Item category will determine in STO process based on

Delivery type= NL

Item category= NORM

Usage= V

Item category= NLN

Prerequisite or master data related for STO process

1.       Material should be maintained in both the plants and material should have purchasing view.

2.       Create receiving plant as customer is for delivery purpose. To creae delivery doc we req ship to party

STO-Configuration:

Path:

SPRO-MM-Purchasing-purchase order- setup stock transport order

1.       Define shipping data for plant:

Go to the receiving plant and assign the customer number and receiving sales area

Go to the supplying plant and assign supplying sales area

2.       Assign delivery type and checking rule:

In this configuration step we assign delivery type NL and checking rule B to the combination of purchase order type UB and supplying plant.

3.       Assign document type , one step procedure, under delivery tolerance :

In this configuration step we assign purchase order type UB to the combination of supplying plant and receiving plant.

In this configuration step we diff weather to process one step  or two step procedure

One step check box:

                If you check this system will treated as one step process and determine 647 movement type. The result is when you do delivery in supplying plant the stock will be automatically updated in receiving plant  

                If you uncheck system will treated as two-step process and determines 641 movement type

                                                                

RETURN SALES ORDER PROCESS SAP SD

Return sales order process in SAP SD

In sap business can be mapped the returns process (customer compensation).


If customer find damaged goods are defective goods then they will inform to company then company will send employee to customers place to cross check the goods. Employee will cross check the goods and he will prepare return note.  

Return note consist of original invoice number, material, quotation and signature of customer and employee.

After preparing return note employee will submit the return note to office then user will create return order with reference to invoice.

When customer send the goods to company then we will create return delivery. Then we create return invoice with reference to retune order.

Return document type – RE(t-code VOV8)

                The main control in Return document type RE is document category- H

Return delivery type- LR (t-code OVLK)

                The main control in return delivery type is Document category - T

Return item category – REN (t-code VOV7)

                The mail controls in return item category
1.       Return  check box should be check
2.       Billing relevance B
3.       Credit active un check


Return billing type- RE (t-code VOFA)

                We will create return invoice with reference to invoice the main control in return billing type is SD document category is O


Return scheduling category- DN (t-code VOV6)

Movement types in returns
651-stock will be added to return stock
653-stock will be added to unrestricted stock
655-stock will be added to quality inspection stock
657-stock will be added to block stock

CUSTOMER MASTER DATA IN SAP

Sales area data:

sales area data consist of four tabs

                        A. Sales tab

                        B. Shipping tab

                        C. Billing tab

                        D. Partner function tab

A. Sales tab:

    

Sales district:

    Sales district is farther classification of sales office It is referred to as customer districts, can be geographical areas or regions

Sales office :

       Mention your Sales office.

Sales group: 

       Mention your Sales group.

Customer group: 

       Grouping of customer who will share the same attributes. system identifies a particular group of customers

Currency:

       We mention customer currency in this field. the system propose this value by default from sales organization

Switch off rounding:

       It indicates whether rounding should be switch of for the customer. if we check this system will not convert the decimal in to nearest value

Order probability: 

        This field Specifies after placing order by the customer what is the chance that customer may cancel the order or decrease the quantity.

Authorization group:

         When ever we are giving access to customer to check his report in SAP. we need to give authorization to each $ every customer authorization will be given by basis consultant.

Item proposal :

           If customer are frequently placing order for similar material every time then we list out all the material in to a document and call that document while creating sales order select the item and copy

Exchange rate type:

            If company is having agreement with the customer for a specific rate which should valid for a month

Price group:

         Group of customer who will share the same price attributes

Customer pricing procedure:

       This field is one of the parameter to determine pricing procedure in to sales document

Price list:

      The price of the product is not common for all the customers. every company will prepare multiple price list basing on the requirement.

Customer Statistic group:

         This field control weather to update customer sales data in to LIS or not

Shipping tab:

Delivery priority:

    You define delivery priorities in this menu option. You can use them to control the delivery of sales orders or order items and therefore give priority to individual customers.n the standard SAP R/3 System, number 1 represents the highest delivery priority. During the selection, delivery items with priority 1 are proposed first.

the purpose of this field is to perform back order process rescheduling 

Order combination:

       If you check this stem will allow to combine multiple orders in to single delivery

Shipping condition:

     This field is one of the parameter to determine shipping point in to sales document line item 

Delivering plant:

       If we mention delivery plant here it automatically determines in to sales document line item

Relevant for POD:

      Proof of delivery is the confirmation sent by the Ship to party upon the reciept of goods. Once you configure the POD in your system, means it wont let you

POD time frame:

       If we mention no of days here and if the acknowledgement has not been received from customer with in those days then system by default think that acknowledgment has been received and will to create invoice

Complete delivery by law:

       If you check this system will not allow to create partial delivery system will not confirm partial quantity

Partial delivery per item:

      This field control whether to allow partial delivery or not it also control how many partial delivery to be allowed

Unlimited tolerance:

      If you check this system will allow to increase or decrees the quantity in delivery document with out any limitation

Billing Document tab:

Rebate;

   Rebate is a prerequisite to process rebate for a particular customer

Price determination:

    This field is applicable only for customer hierarchy

Invoicing dates:

    If customer requirement is invoice should be raise only on month end for all the dispatches made during the month then we use invoicing dates.

Incoterms:

    This is an agreement between shipper and receiver for successful completion of delivery 

Terms of payments:

    Its an agreement between company and customer for the no of days given to make the payment  

Payment guaranty procedure:

     We use this field for export customer 

Credit control area:

    It is an organizational unit which is responsible for all the credit activity happen in the company

Account assignment group:

    This field is one of the parameter to determine G/L account while posting the invoice  value in to accounting

Tax classification:

     This field control when the customer is laible for tax or not

Partner functions:

Sold to party:Who place the order

Ship to party: Who receiving goods

Bill to party: Who will receive bill

Payer: Who will make the payment

CUSTOMER MASTER DATA IN SAP

            The customer master record is the basis for all sales transactions as well as deliveries and payments. Customers master records can represent different entities based on the role they play in the transaction. Customer master data ia a collection of records related to a customer, sales area, and other transaction related units. The data related to all the customers, including intercompany customers and one-time customers, must be stored in customer master record

 The structure of master data in the customer master record is comprised of these three areas:

(A)  General data

(B)  Company code data

(C)  Sales area data

(A)             General data:

General data represents a set of data independent of any organizational units of the SAP system. It contains data related to address, control, payment transactions, marketing, uploading points, exports, and contact persons. This data is only identified by the customer number, and is not specific to the company code or sales area. Maintaining the data is possible from both the company code view and the sales and distribution view.

(B)             Company code data :

It represents a set of the data used by the accounting department of an organization. It consists of the data related to account management , payment transaction correspondence, and insurance. This data is mostly of interest to the accounting department. It includes, for eg, information on the reconciliation account and dunning procedures and withholding tax. This data applies to only one company code.                      

(c) Sales area data:

            It Represent a set of data related to the SD module of the SAP system. It consists of data related to orders, shipping billing, and partner functions. This data is only interest for the sales and distribution area. It includes, for example, data on pricing or shipping. This data only applies to one sales area, and therefore is dependent on the sales structure.

T-code to create Customer master

XD01 - Create Customer (Centrally)   

XD02 - Change Customer (Centrally) 

XD03 - Display Customer (Centrally) 

VD01 - Create Customer (Sales) 

 FD01 - Create Customer (Accounting)

Path

·         SAP Easy access

·         Logistics

·         Sales and Distribution

·         Master data

·         Business partner

·         Customer

·         Create

Mention require details

Account Group:

This is where you select whether your customer is a sold-to party, ship-to party, bill-to or any other type of partner that may exist in your system.

Company Code

Sales Organization

Distribution Channel

Division

Then click on Enter

Now I am going to explain fields In Customer Master

General data:

Address tab : 

          It consist of the personal information of the customer Eg. Name Phno, and Email Id Etc. in the general data section Transportation zone in Sales and Distribution it represents regional zone of goods recipient.  

Control data tab :

          It consist of the tax information of the customer. this tab will be taken care by FI- consultant

Payment transaction:

           It consist of the customer mode of payment details 

Marketing tab:

          it consist of Nelsen id, customer classification, industry sector, industry code, regional code regional marketing, key figures

Unloading Point:

          It is a place where we unload the goods at customer location. some customers will have multiple unloading points. we need to maintain  the data of all which will help to plan the dispatch.

Export data: 

We use this tab the customer is located in outside country

Contact person:

      Contact person is the Employee of the customer , whom we meet for various activities .

Company code data:

 Click company code data on the application tool bar

   account management tab

       reconciliation account:

                 When we create invoice the back ground system will post the accounting entry the accounting entry is customer account debit to revenue account credit. from the customer account system fix G/L account for reconciliation account 

To continue read pls click on below link

http://sapsdknowledge.blogspot.in/2014/08/customer-master-data-part-2.html