EDI Order Response

[Former Member]

Hi,

How can i check the net price calculations done for a particular item on the sales order response. My problem is.

The value sent in field vprei is having a netprice value and from this i have to deduct bill back condition value.and this should be happen only to the sales order response (EDI). how can i implement this senario.

[Former Member]

Hi,

How can i check the net price calculations done for a particular item on the sales order response. My problem is.

The value sent in field vprei is having a netprice value and from this i have to deduct bill back condition value.and this should be happen only to the sales order response (EDI). how can i implement this senario.

[Former Member]

Chindam,

Are you already using EDI to send the order response?

What is the message type that you are using?

Thanks

Ganesh.S

[Former Member]

Hi Ganesh,

Yes we are using the EDI to send the Order response to the customers the message type we are using is ZORDRSP.

This message type Process code SD10 and i guess this process code calls the function module IDOC_OUTPUT_ORDRSP to fill the IDOC details and send.

But when i keep a break point at the this function module IDOC_OUTPUT_ORDRSP and try to debug, the program is not comming to debug mode but the idoc is created. i dont understand is some thing wrong in my procedure. how can debug to see what is the function module which is used to fill the idoc and send it to customer.

Thanks.

[Former Member]

For outbound you have follow below steps to debug.

1) Cllick header-->output

2) Repeat output type

3) Select output type and click Further data and select dispatch time to 1(Send with periodic schedule job).

4) Save.

5) Go to Transaction WE15 or execute RSNAST00 program

6) Select your output type..input object key-->nothing but document number(eg..sales order number).

select output type and transmission medium.

7) Now breakpoint stop at your user exit.

"Reward point if usefull".

Thanks,

Narayan

[Former Member]

Hi Praveen,

Narayanan's steps will surely help you debug the program.

Please also check your source code for the program ZXVEDU01/02.

This is one of the exits that you can use or already using ( I am suspecting this because it is a Z message type ) wherein you can populate the value.

Thanks

Ganesh.S

[Former Member]

Thanks a lot guys problem solved.

[Former Member]

Visit the followingl links:

https://wiki.sdn.sap.com/wiki/display/ERPLO/SD+Configuration

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/cin%2bconfiguration

Also, visit the following threads:

/message/3505991#3505991 [original link is broken]

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.

Interesting &important link to learn much more about configuration & business process is as under:

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.

All Standard Reports which are available are as under:

SAP Easy Access: Information Systems -> Logistics -> Sales and distribution ->

1. Customer -> Incoming orders / Returns / Sales / Credit memos / Sales activities / Customer master / Conditions / Credit Master Sheet

2. Material -> Incoming orders / Returns / Sales / Credit memos / Material master / ...

3. Sales organization -> Sales organization / Sales office / Sales employee

4. Shipping point -> Deliveries / Returns

5. SD documents -> Orders / Deliveries / Billing documents ...

& so on.

Some of the Standard reports in SD are:

Sales summary - VC/2

Display Customer Hierarchy - VDH2

Display Condition record report - V/I6

Pricing Report - V/LD

Create Net Price List - V_NL

List customer material info - VD59

List of sales order - VA05

List of Billing documents - VF05

Inquiries list - VA15

Quotation List - VA25

Incomplete Sales orders - V.02

Backorders - V.15

Outbound Delivery Monitor - VL06o

Incomplete delivery - V_UC

Customer Returns-Analysis - MC+A

Customer Analysis- Sales - MC+E

Customer Analysis- Cr. Memo - MC+I

Deliveries-Due list - VL04

Billing due list - VF04

Incomplete Billing documents - MCV9

Customer Analysis-Basic List - MCTA

Material Analysis(SIS) - MCTC

Sales org analysis - MCTE

Sales org analysis-Invoiced sales - MC+2

Material Analysis-Incoming orders - MC(E

General- List of Outbound deliveries - VL06f

Material Returns-Analysis - MC+M

Material Analysis- Invoiced Sales - MC+Q

Variant configuration Analysis - MC(B

Sales org analysis-Incoming orders - MC(I

Sales org analysis-Returns - MC+Y

Sales office Analysis- Invoiced Sales - MC-E

Sales office Analysis- Returns - MC-A

Shipping point Analysis - MC(U

Shipping point Analysis-Returns - MC-O

Blocked orders - V.14

Order Within time period - SD01

Duplicate Sales orders in period - SDD1

Display Delivery Changes - VL22