Solved: reg SD

Former Member · ‎05-22-2007

Hi to all,

i'm new to this SD module and i need basic information and work flow for SD.

Plz help me

Former Member · ‎05-22-2007

Dear Kumar,

Workflow scenarios for SD:

Processing credit memo requests:

Credit memo requests normally need to be checked by the employee who entered them as well as approved by an additional decision-maker. The value of the credit memo determines who is able to approve it.

Once a credit memo request is created, the system normally creates a billing block. This block prevents you from billing the credit memo request and can only be removed by an authorized employee.

Using the workflow, you can represent the whole business process, with all the people involved, for approving credit memo requests within your company. This enables you to process credit memo requests simply and efficiently. If you do not use the workflow, the system does not control the process flow so you will have to organize the steps in credit memo processing yourself.

If the value of a credit memo request is below a minimum value, the system automatically releases it for billing by removing the billing block.

If the credit memo request exceeds a certain value, the system automatically informs the employee responsible. She or he receives a work item in their inbox and can process it directly from there.

The employee responsible can cancel, release, or process a credit memo request.

If the employee cancels the request, the system automatically creates a reason for rejection in the credit memo request and ends processing.

If the employee releases the request, the system automatically removes the billing block in the credit memo request and releases it for billing.

If the employee processes the request, she or he can use all the functions available in the change transaction.

The people informed by the workflow do not need to know either the name of the transaction or the menu path of the transactions involved.

Change master contract:

In companies that use a high number of contracts, several contracts are often subject to the same business controls (for example, agreements on pricing or terms of payment). Contracts with the same business requirements can be linked to a master contract as lower level contracts. The general requirements stipulated in the master contract are then valid for all the lower level contracts assigned to it. The referencing procedure acts as a set of rules in Customizing which enables you to control which data from the lower level contract can be changed and which data has to agree with the master contract. This ensures that the defined requirements remain consistent in all the assigned lower level contracts.

If any of the fields in the master contract that have to be identical to the equivalent fields in the lower level contract are changed, these fields must also be changed in all assigned lower level contracts.

The workflow enables you to control the process of changing master contracts simply and efficiently. All the lower level contracts assigned to a master contract are updated and the employees involved are automatically informed if an error occurs, such as an application error or if the document is blocked.

Removing errors in internet sales order:

In the Internet application component Online Store, customers can obtain quotes and enter orders over the Internet. They can choose to pay either by invoice, credit card or cash on delivery.

If a quotation or order cannot be created because certain master data or Customizing settings are missing or not properly maintained, the transaction is cancelled and an error message is displayed in the customer’s browser.

This workflow enables the relevant associates to be informed automatically about the error so that they can be corrected as quickly as possible.

Handling exceptions at Goods Receipt:

You can use the functions of store goods receipt for stores that donot have a direct link to the central SAP System and therefore post their goods receipt in a store merchandise management system. This goods receipt data is then transferred in the form of an IDoc to the central SAP System, where it is processed automatically. If the data is complete and error-free, the goods receipts of the stores are posted in the central system.

In IDoc inbound processes, exceptions may occur, and you can process these using workflow. Exceptions are situations in which the system is not able to process data automatically, because information on the goods movement item is missing.

Exceptions therefore usually apply to a single goods movement item. Exception handling is required, for example, if one of the following situations occurs:

The open goods receipt quantity is too low
Quantity variances were determined in the goods receipt check
The system could not uniquely assign a purchase order or delivery to the store goods receipt
The system could not determine a purchase order or delivery to the store goods receipt
The system could not expand a shipping unit into its individual articles
The workflow described below is used to handle these exceptions.

Reward points if this is helpful.

Regards,

Naveen.

Former Member · ‎08-08-2007

HI please send the document as well

sapsamita@yahoo.com

Former Member · ‎08-07-2007

hi,

go throught the SAP library which is the best and extensive source of information. Also you can see Glynn C williams text book. Otherwise we cant really figure something as basic information. Because it all depends on the kind of project one would be working.

However you can keep in touch with this forum to see the happening.

Thanks

Sadhu Kishore

Former Member · ‎05-22-2007

Dear kumar,

Please visit the website:

www.sap-img.com/sap-sd.htm.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

P.S. you can send me a mail at my mail id rakeshsinghchauhan@gmail.com for any specific details

Former Member · ‎05-22-2007

Link: http://help.sap.com/

Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.

Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on ...........

Regards,

Rajesh Banka

Reward points if helpful.

Former Member · ‎05-22-2007

Link: http://www.sap-img.com/

Topic: Free ABAP eBook Download

SAP MM, SD, FI, PS, PP, PM, HR, System Tables

Regards,

Rajesh Banka

Reward Points if helpful.

Former Member · ‎05-22-2007

SD Configuration:

Enterprise Structure:

1. Maintaining Sales Organization

Sales Organization is an organizational unit responsible for the sale of certain products or services.

IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization

2. Assigning Sales Organization to Company Code

This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code

3. Maintaining Distribution Channel

Distribution Channel is the way, in which Products or Services reach Customers.

IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel

4. Assigning Distribution Channel to Sales Organization

This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization

5. Maintaining Division

Division is a way of grouping materials, products, or services.

IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division

6. Assigning Division to Sales Organization

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization

7. Setting up Sales Area

All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.

IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area

8. Assigning Sales Organization- Distribution Channel- Plant

Plant is created ny MM Consultant.

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant

9. Define Shipping Points

Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.

IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point

10 Assigning Shipping Point to Plant

This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.

IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant

Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.

11. Defining Common Distribution Channels for Master Data

Use

The purpose of this activity is to define distribution channels which have common master data..

Procedure

Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels

Transaction Code: VOR1

12. Defining Common Divisions for Master DataUse

The purpose of this activity is to define distribution channels which have common master data..

Procedure

Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division

Transaction Code: VOR2

Pricing Procedure

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

Normal Sales Order Cycle:-

Step 1: Sales Document Type

IMG > Sales and Distribution > Sales > Sales Documents >

Sales Document Header:

1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.

2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.

3. Assign Sales Area To Sales Document Types:

A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.

B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.

Sales Document Item:

1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.

2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category

Schedule Line:

1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.

2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.

Step 2:

IMG > Logistic Execution > Shipping > Deliveries >

1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.

3. Define Number Ranges for Deliveries: Ensure to maintain number range.

Step 3:

IMG > Sales and Distribution > Billing >

1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Number Range For Billing Documents: Ensure to maintain number range.

3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.

The configuration differs from scenario to scenario & requirement of the client.

Regards,

Rajesh Banka

Reward point if useful.