Important Tables for Sap Sd

(1)

Important Tables for SAP SD

Sales and Distribution:

Table Description Customers KNA1 General Data

KNB1 Customer Master – Co. Code Data (payment method, reconciliation acct)

KNB4 Customer Payment History

KNB5 Customer Master – Dunning info KNBK Customer Master Bank Data KNKA Customer Master Credit Mgmt.

KNKK Customer Master Credit Control Area Data (credit limits)

KNVV Sales Area Data (terms, order probability) KNVI Customer Master Tax Indicator

KNVP Partner Function key KNVD Output type

KNVS Customer Master Ship Data KLPA Customer/Vendor Link

Sales Documents VBAKUK VBAK + VBUK

VBUK Header Status and Administrative Data VBAK Sales Document - Header Data

VBKD Sales Document - Business Data VBUP Item Status

VBAP Sales Document - Item Data VBPA Partners

VBFA Document Flow

VBEP Sales Document Schedule Line

VBBE Sales Requirements: Individual Records SD Delivery DocumeLIPS Delivery Document item data, includes referencing PO

LIKP Delivery Document Header data Billing Document VBRK Billing Document Header

VBRP Billing Document Item

SD Shipping Unit VEKP Shipping Unit Item (Content) VEPO Shipping Unit Header

SD Master Records

———————————————————

Business Partners

XD01/VD01 Create Customer Master Centrally XD02/VD02 Change Customer Master Centrally

XD04/VD04 Display Changes to the Customer Master Centrally XD05/VD05 Block or Unblock a Customer

(2)

OV50 Display of Changes for Customer

V-07/VD01 Create One-Time Customer (Sales) V-08/VD01 Create Payer (Centrally)

V-09/VD01 Create Ordering Party (Centrally)

Item Proposal

VA51 Create Item Proposal VA52 Change Item Proposal

Conditions

VK11 Create Condition VK12 Change Condition

VK14 Create Condition with Reference

SD Sales Process

———————————————————

Sales Inquiry

VA11 Create Inquiry VA12 Change Inquiry VA15 List of Inquiries

Sales Quotation

VA21 Create Quotation VA22 Change Quotation VA25 List of Quotations SDQ1 Expiring Quotations SDQ2 Expired Quotation SDQ3 Completed Quotations

V.04 Display Incomplete Quotations

Scheduling Agreement

VA31 Create Scheduling Agreement VA32 Change Scheduling Agreement VA35 List of Scheduling Agreements

V.05 Display Incomplete Scheduling Agreements

Contracts

VA41 Create a Contract VA42 Change a Contract VA45 List of Contracts

V.06 Display Incomplete Contracts SDV1 Display Expiring Contracts SDV2 Display Expired Contracts SDV3 Display Completed Contracts

(3)

Sales Order

VA01 Create a Sales Order VA02 Change a Sales Order VA05 List of Sales Orders

V.02 Display Incomplete Sales Orders (Sales Order Error Log) V.14 Display Blocked Orders

SDO1 Display a List of Orders Within Time Period

Debit Memo Request Processing

VA01 Create a Debit Memo Request VA02 Change a Debit Memo Request VA05 List of Debit Memo Requests

V.14 Display Blocked Debit Memo Requests SDO1 Display a List of Orders Within Time Period

Credit Memo Request Processing

VA01 Create a Credit Memo Request VA02 Change a Credit Memo Request VA05 List of Credit Memo Requests

V.14 Display Blocked Credit Memo Requests SDO1 Display a List of Orders Within Time Period

Returns

VA01 Returns Order VL01N Returns Delivery VF01 Credit for Returns

Shipping and Transportation

———————————————————

Delivery

VL01N Create Delivery

VL02N Change Outbound Delivery

VL22 Display Delivery Change Documents VL71 Output from Deliveries

VL10A Process Delivery Due List

Picking

VL06O Sel. Outbound Deliveries for Picking

Post Goods Issue

VL06G Deliveries for Goods Issue

VL09 Cancel Goods Issue for Delivery Note VL23 Goods Issue (Background)

(4)

SD Billing

——————————————————— VF01 Create Billing Document

VF02 Change Billing Document VF04 Process Billing Due List VF05 List Billing Documents VFX3 Release Billing Documents VF31 Output from Billing

VF11 Cancel Billing Document VKM1 Blocked SD Documents VKM2 Released SD Documents

Sales Information System

——————————————————— MCTA SIS: Customer Analysis – Selection MCTC SIS: Material Analysis – Selection MCTE SIS: Sales Org. Analysis – Selection V/LD Execute Pricing Report

SAP SD Transaction codes List

I found a way to know hidden customizing Tcodes.

Before executing customizing task you desire, point it and go to Edit-Display IMG Activity. Then mark activity.

Go to T.Code se16 and type in CUS_IMGACH table. Execute.

Paste IMG Activity and run.

You will see Tcode that belongs to IMG Activity.

Where do we maintain "Item Category Usage" at the master level?

Spro --> Sales and Distribution --> Sales --> Sales Documents --> Sales Document Item --> Define Item Category Usage

Item Category Usage: item category usages which control the usage of an item. Item category usage controls, for example, the system response if during document processing an item does not refer to a material but to a text item. Item category usage can also be maintained via the item categories

(5)

In contracts we are creating quantity contract and value contracts in that we only put the validity period after validity period that contract will close,but customer want before one month closing the period system should alert with popup box like this contract is going to close, for this sales manager can follow up the customer for renual the contract.

Getting a pop-up when the Contract is going to expire is not a Standard SAP thing. For this you need to do some programming. Instead of this the Std system has a reminder system where in the open Contracts and Quotaions are popped up when you about to create a sales order.

This setting is in the Sales order header ,

Goto -- VOV8 --- Quotation and Outline agreement messages

If you want to have different number range for different sales area where the settings to be done.

Number Rage are use to define what number to be assign to sales document type. Number range can be assign Internal or external.

In internal number range system automatically assign a number to sales document according to number range define in system.

In External number range user manually assign number to sales document. For Assigning Number Range use T-Code VN01

Choose Intervals ---- Define your number range

Task Specifc SD Transaction Codes 1

How to configure tax?

Use the following Tcodes:

OBQ1 --- CONDITION TABLE OBQ2 --- ACCESS

(6)

OBBG --- ASSIGN COUNTRY TO TAX PROC OVK3 --- CUSTOMER TAX CATEGORY OVK4 --- MATERIAL TAX CATEGORY OVK1 --- TAX DETERMINATION RULES OVK6 --- ASSIGN DELIVERY PLANTS

and thenVK11 to maintain the condition record for the tax rate.

I raise a sales order and is getting a error stating that "sales area is not defined".

1) At SPRO-->SD-->Sales header-->Assign Sales area to Sales document - Combine your Sales Organisations, Distribution Channels & Divisons

2) At VOPA-->Assign Partner Determination procedure to your Account Group of Customer Master you are using.

3) At VOPA--> Assign Partner Functions to your Account Group & Partner Determination procedure

Steps to create a Vendor Master Data at the client level and how do we extend it to different company codes?

Follow the following steps:

1. Create a vendor account group OBD3

2. Define no. range for vendor account group XKN1 3. Assign number range to Vendor account group OBAS 4. Define tolerance Group for vendor OBA3

5. Create 2 GL accounts FS00 a) Purchases A/c

b) S. creditors A/c

6. Create Vendor master data XK01

7. change/block vendor master data XK02/XK05 8. Define document type and no. range OBA7 a) KA

b) KG c) KR

d) KZ *-- Vandna

How to find the strategy group in sap sd?

Menu path for Strategy Group is:

Spro --> Production --> Production Planning --> Demand Management --> Planned Independent Requirements --> Planning Strategy --> Define Strategy Group. OPPT -- Maintain Starategy Group

(7)

We can see Strategy Group in Material Master Record - MRP 3 - Planning -- Strategy Group.

10 - For Make to Order 20 - For Make to Stock

SAP SD Tips by: Javier

The most frequently used transaction codes are as follows:

1. VS00 - Master data 2. VC00 - Sales Support 3. VA00 - Sales 4. VL00 - Shipping 5. VT00 - Transportation 6. VF00 - Billing Others as follows: At Configuration:

1. VOV8 - Define Sales documents type (header)

2. OVAZ - Assigning Sales area to sales documents type 3. OVAU - Order reasons

4. VOV4 - Assign Item categoreies(Item cat determination) 5. VOV6 - Scedule line categories

6. OVAL - To assign blocks to relevant sales documents type 7. OVLK - Define delivery types

8. V/06 - Pricing

9. V/08 - Maintain pricing procedure 10.OVKP - Pricing proc determination 11.V/07 - Access sequence

Enduser:

1. Customer Master Creation-VD01 and XD01 (for full inclu company code) VD02 - Change Customer

VD03 - Display Customer

VD04 - Customer Account Changes VD06 - Flag for Deletion Customer XD01 - Create Customer

XD02 - Modify Customer XD03 - Display Customer 2. Create Other material ----MM00

(8)

4. CO09- Material availability Overview

5. VL01 - Create outbound delivery with ref sales order 6. VL04 - Collective processing of delivery

7. VA11 - Create Inquiry VA12 - Change Inquiry VA13 - Display Inquiry

Sales & Distribution

Sales order / Quote / Sched Agreement / Contract

· VA01 - Create Order · VA02 - Change Order · VA03 - Display Order · VA02 - Sales order change · VA05 - List of sales orders

· VA32 - Scheduling agreement change · VA42 - Contract change

· VA21 - Create Quotation · VA22 - Change Quotation · VA23 - Display Quotation

Billing

· VF02 - Change billing document · VF11 - Cancel Billing document · VF04 - Billing due list

· FBL5N - Display Customer invoices by line · FBL1N - Display Vendor invoices by line

Delivery

· VL02N - Change delivery document · VL04 - Delivery due list

· VKM5 - List of deliveries

· VL06G - List of outbound deliveries for goods issue · VL06P - List of outbound deliveries for picking · VL09 - Cancel goods issue

· VT02N - Change shipment · VT70 - Output for shipments

General

· VKM3, VKM4 - List of sales documents · VKM1 - List of blocked SD documents · VD52 - Material Determination

(9)

KONV Conditions for Transaction Data KONP Conditions for Items

LIKP Delivery Header Data

LIPS Delivery: Item data

VBAK Sales Document: Header Data VBAP Sales Document: Item Data

VBBE Sales Requirements: Individual Records VBEH Schedule line history

VBEP Sales Document: Schedule Line Data VBFA Sales Document Flow

VBLB Sales document: Release order data VBLK SD Document: Delivery Note Header VBPA Sales Document: Partner

VBRK Billing: Header Data VBRP Billing: Item Data

VBUK Sales Document: Header Status and Administrative Data VBUP Sales Document: Item Status

VEKP Handling Unit - Header Table

VEPO Packing: Handling Unit Item (Contents) VEPVG Delivery Due Index

Transaction Action:

J1I2 - Prepare a sales tax register

J1I3 - Create outgoing excise invoices in batches J1I5 - Update the RG 1 and Part I registers

J1IEX - Incoming Excise Invoices (central transaction) J1IEX_C - Capture an incoming excise invoice (excise clerk) J1IEX_P - Post an incoming excise invoice (excise supervisor) J1IF01 - Create a subcontracting challana

(10)

J1IF11 - Change a subcontracting challan J1IF12 - Display a subcontracting challan

J1IF13 - Complete, reverse, or recredit a subcontracting challan J1IFQ - Reconcile quantities for subcontracting challans

J1IFR - List subcontracting challans

J1IH - Make a CENVAT adjustment posting J1IIN - Create an outgoing excise invoice

J1IJ - Assign excise invoices to a delivery for sales from depots J1INJV - Adjust withholding tax Item

J1INREP - Reprint a withholding tax certificate for a vendor J1IQ - Year-End Income Tax Depreciation Report

J1IR - Download register data

J1IS - Process an excise invoice (outgoing) for other movements J1IU - Process exemption forms

J1IW - Verify and post an incoming excise invoice

J1IX - Create an incoming excise invoice (without reference to purchase order) J2I8 - Transfer excise duty to CENVAT account

J2IU - Remit excise duty fortnightly J2I9 - Monthly CENVAT return J1IG - Excise invoice entry at depot

J1IGA - Create additional excise entry at depot J2I5 - Extract data for excise registers

J2I6 - Print excise registers

Standard SAP SD Reports

Reports in Sales and Distribution modules (LIS-SIS):

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

(11)

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

SAP Sales and Distribution Frequently Asked Question

Master Data

Q: Some materials have been blocked for procurement and production. Even though

deletion flag is set for a material/plant level, the order can be still entered ( with a warning message). Is there a way to block such transactions for a material flagged for deletion?

A: Sales Status field in the sales organization view of the material master may be used to

block any transaction for the material.

Q: We can define our own exchange rate types and use them instead of the defaulted types, 'M', 'B' and 'G'. How can we overwrite default types in SD?

A: Exchange rate gets copied from the customer master record. Exchange rate types are

(12)

Shipping

Q: The PL00 condition is fine in delivery. But when we try to print to either the screen or

printer, an error V1032 occurs. Why?

A: In order to use the Packing list PL00 (packing slip in delivery) you must do 'Packing'

in the delivery note (edit->packing)

Q: we have to enter a shipping point while creating a delivery. Is it possible to create delivery without shipping points?

A: When you are releasing a sales order, choose Sales document -> Subsequent

functions-> Create delivery, then the shipping point will be brought in from the sales order. In all other scenarios you have to key in the shipping point. The above described scenario will only work if all items on the sales order are to be shipped from the same shipping point.

Billing

Q: SAP allows a non-inventory item and an inventory item to be in the same document

till delivery but splits at the time of creation of billing document. Can we combine a non-inventory item with an non-inventory item in one invoice? Can we treat it as a value item in sales order so that it is priced and then make it as a text item in delivery documents so that it appears in the same invoice and does not split?

A1: Make the non-stock material deliverable, but not pickable. Both items will carry into

the delivery, and therefore appear on the same invoice.

A2: Change the copy rule for orders->invoices and deliveries->invoices to specify that

invoice combination is permitted. However note that for system to create combined invoices, PO number, payment terms, sales organization, and distribution channel must be identical. Else undesirable combinations may be created by the system.

Pricing Conditions

Q: It is impossible to price at the material level (matnr) , when a material has a pricing

reference (mvke-pmatn) set up against it in the master data. Pricing always look for the pref, even if a price is set up against the material and not the pref. How can we price by material and pref?

(13)

A: The field used to look up at the price is defined in Access sequence. You may find a

step with PMATN as material number. If you insert a step with MATNR then the system will first look for the material, if not found (use the exclusion tick box) it will look for the pref.

Customizing

Q: We generated a new condition table. Assigned the condition to access sequence.

Created a condition record. Access sequence is assigned to the output type. But when we create a billing document, output screen comes up blank for the output type. When we look up Determination Analysis, we get an error "Note 524 Access not made (Initialized Field)". What else is required to be done?

A: Assign output determination procedure to the header of the document and the output

type.

Q: How can we set up to have the VAT# be accepted in the Ship-To Master File Data Control screen?

A: IMG->Fin. Acct.->AR and AP ->Customer acct->Master Record -> Prepare to Create

Customer-> Define Acct. Group.

Q: We want to explode Bill of Material automatically at time of Order entry and explode an Equipment BOM in the sales order. What are the setting required?

A: Use an item category that is configured for bills of material for having a sales BOM to

explode automatically.

Standard SAP item categories are :

TAQ - Pricing and inventory control take place at the BOM header level TAP - Pricing and inventory control take place at the BOM item level

These can be automatically derived using the item category groups ERLA and LUMF, respectively.

Q: How can we make the Customer Group 1 (or 2, 3, 4, 5) a mandatory field?

A: Logistic General-> Logistics Basic Data: Business Partners -> Customers -> Control

-> Define account groups and field selection for customer

Choose Customer Acct. GR. (double-click). -> Field Status: Sales data (double click) -> sales (double click) .Check the radio button against Customer Gr as REQ. ENTRY. Save the settings to make customer GR entry mandatory .

Q: Is there an user exit to copy the data into planning table?

A: Use user exit MCP20001 and include ZXSOPU01.

(14)

Q: We get a report screen: "Goods issue: Problem Log" during the

delivery process

when activating Post Goods Issue button. We want to include our own error message to this list if the selected batch is not on a customer defined table. What is the best way?

A: Try User exit - USEREXIT_SAVE_DOCUMENT_PREPARE

Link Between SAP SD, MM & FI

1. In SAP you will always get integration with other modules. SD will interact with FI, MM will interact with SD :-

1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped

directly to your customer).

1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.

2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc. *-- Shahee

The link between SD and MM :-

1. When you create sales order in SD, all the details of the items are copied from Material master of MM.

2. MRP and availibility check related data is also taken from MM although you control this data in SD also.

3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.

(15)

4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.

There are many such links between SD and MM.

Now the link between SD and FI :-

1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.

Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.

2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI

3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM

SD Integration points with other modules

SD module is highly integrated with the other modules in SAP.

Sales Order –

Integration Points Module •Availability Check - MM •Credit Check - FI •Costing - CO/ MM •Tax Determination - FI •Transfer of Requirements - PP/ MM Delivery & Goods Issue –

Integration Points Module •Availability Check - MM •Credit Check - FI •Reduces stock - MM •Reduces Inventory $ - FI/ CO •Requirement Eliminated - PP/ MM Billing

-Integration Points Module •Debit A/R - FI/ CO •Credit Revenue - FI/ CO •Updates G/ L - FI/ CO (Tax, discounts, surcharges, etc.)

•Milestone Billing - PS Return Delivery & Credit Memo

-Integration Points Module •Increases Inventory - MM

(16)

•Updates G/ L - FI •Credit Memo - FI •Adjustment to A/R - FI •Reduces Revenue - FI

Tips by: Subha

SD Transaction Code Flow:

Inquiry / Document type IN

Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP Quotation / QT

Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP Purchase Order PO

Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO. Sales Order OR

Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP Delivery LF

Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS Billing MN

Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP

To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no.

To create vendor tcode is

xk01(create), xk02(change) , xk03(display) Tables are lfa1.

To create custmer tcode is xd01, xd02, xd03. Table is kna1.

After creating sales order using this no we can create delivery note tcode is vl01.

Why Do We Assign Division to Sales Organisation

In SAP, why do we assign division to Sales organisation not to distribution channel?

In SAP Business Process

Sales Area= Sales Org.+Dist.Channel+Division.

(17)

Its Triangular intraction Sales organization / \ / \ Dist.Channel<--->Division

Sales Org controls Distribution Channel and Division

Distribution Channel: The channel that is choosen the organization to make their product reach the end customer.(Network)

Division: Ex: HLL---> Detergents, Out of Home,Food Products,Health Care Sectors/Departments

TATA Motars: Trucks/Bus,Cars,Heavy Vechiles Etc...

Please note it is not: Sales organization | | Dist.Channel | | Division

Division is an Oragaizational Unit.

The Division in the Material Master is not an Organizational Unit that can be used to maintain related fields. It is a field which is used to uniquely assign a material to a Division.

How To Do Master Record Mass Maintenance

Which master records mass maintenance can be done? What do you mean by mass maintenance?

Mass maintainance in MM-

1. Mass Maintainance means to change a master data or transactional data in mass 2. SAP has provided Mass Maintainance for many objects

(18)

Examples:Material masters, BOMs, Routings, Workcenters in PP In MM --> Inforecords, PO,s Preqs etc

To do master record mass maintenance

You can use tcode MASS and then select your Object type or there is few specific mass maint. Tcode is available like for PO = MEMASSPO etc. but you can use MASS also for that you need to select the object type for PO

Tips for mass modification:

Use object type BUS1001 and generate. Then you have to know the tables where the field you want to modify is. Pick the fields in their folder and generate again. Then in

selection pick the materials or use other selection criteria. Generate again.

In the upper side of the screen insert the data and click the button 'carry out a mass change'.

Save and leave.

Master records mass maintenance can be done:

Material master, info record, vendor, PO, PR, etc.

What do you mean by mass maintenance?

MASS maintenance means - suppose you want to change prticaulr field of material for all the mateirl of certian plant or all the plant you can do using mass like wise for certian PO value if you want to cahnge you can use mass.

There a lot of transactions for specific mass changes. MASS is also one of the transactions among them.

- Mass Change in material master. MM17 - Mass change in BOM. CS20

- Mass change in work center. CA85 - Mass change in Reference opn set. CA95 - Mass change in PRT. CA75

- SU10 Mass changes to User Master.

- SU12 Mass Changes to User Master Records. - CO44 Mass processing of orders.

- F.80 Mass reversal of documents. - FOFO Mass release.

(19)

- FOVX Mass processing of offers.

- IMAM Mass maintenance of approp.requests. - KE55 Mass Maintenance PrCtr Master Data. - XD99 Customer master mass maintenance. - XK99 Mass maintenance, vendor master.

Serial Number Management In SAP SD

By: Rob

I am following the below step: 1. Serial number profile is created.

2. Assigned sales order procedure (SDAU) and delivery proceedure to serial number (SDLS).

3. Profile is assigned in material master record

4. Assume there is a stock of 10 quantity without serial number (you can do 561 for initial stock posting )

5. IQ01 created serial number for all the 10 stock. 6. VA01 created sales order for one quantiy

7. Assigned one serial number for this material

8. Sales order is saved and delivery and PGI is done for the same serial number and material

9. MMBE stock is reduced with one quantity

10. MB51 if check the material document in serial number TAB i can see a message that "The material is managed in serial numbers"

So now my question is why I can't see serial number in material document? How can able to see that? what is the configuration required?

Whatever settings you have maintained is correct. I shall share as to what happens in our business process.

VA01- Sales order Vl03 - Delivery LT03- Transfer Order

After transfer order there is a transaction used ZL02 where in the delivery number is entered and on executing, a screen pops up asking for the serial number. Here we enter the serial number maintained for the material and is got from MMBE. And the serial number is captured for the material.

(20)

Pls check for the serial numbers in MMBE and I suppose a program needs to be created by an ABAPer for the serial number to be fetched and a transaction to be

created and associated with the program.

I need Serial Number Profile tables as soon as possible.

T377P - Serial Number Management Profiles

T377P_T Texts for Serial Number Management Profiles T377X Documents Allowed for Serial Number Management T377X_T Texts for Serial Number Management Documents T5KSN ROE Serial Number

SERI Serial Numbers

EQBS Serial Number Stock Segment EQSE Serial Number Records IQ09 - Check Material Serial No

In outbound delivery, post goods issue failed because of serial number, but this serial number was not assigned to any other material.

Check the serial number and material with IQ03. Serial number is material specific.

When I looked at the IQ03, for the serial no "#162559019S.", I realized that the status is still remain as EDEL and ESTO.

Supposingly, the status should only has ESTO. Is there a way to remove the status "EDEL"?

Go to IQ02, do the following steps:

1. Go to edit -> Special serial number function -> manual transaction 2. Choose "to stock"

The status should be ESTO now. Try it.

EDEL status shows that it is assigned to a delivery. Change it by going into IQ02 --> Edit --> Sp.Serial number Functions --> Manual Transaction and make it 'to stock'

If the serial number has status EDEL ESTO that means the serial number is assigned to the Delivery, reversal PGI has not been completely performed.

Once you do that then only this will come as ESTO.

Please check your SD document flow if all the documents have been reversed. Click the Status of Serial Number Master record.

(21)

- ESTO status In the warehouse. means .. open..

- EDEL (Assigned in delivery note). According to this status, transaction 'Goods issues' is not allowed.

- ECUS At customer site

Sales Office Address, Change and Assignment

SAP Functional ==> SD In SAP

Where to change the ADRNR field for a particular sales office?

SPRO --> Enterprise Structure --> Definition --> Sales & Distribution --> Sales Office --> Define Sales Office. Here go to the address & change the address & the new address will reflect in the output.

Table in which sales office data is stored.

In which table name address of the sales office (SD ) is stored. Also tell in which table, description of the sales office is stored.

table TVBUR-vkbur is the sales office

table tvbur it contains a field called address number. ADRNR take that field(ADRNR) and compare with table ADRC-ADRNR.

in table ADRC you will find name, description, address and all other data. table TVKBT -- description of sales office.

Assignment of Single sales office to multiple sales organizations.

We have a scenario where we need to Assign single sales office to multiple sales organizations in CRM. When I am trying to assign sales office to more than one sales organization 1st assignment between Sales office and Sales Org is getting deleted, and only the 2nd assignment is available.

At sales office level in Function tab, it is showing only the assigned sales

Organization (only one sales org), how to assign one more sales org to this sales office here.

(22)

The assignments are on the lower node. Which means you will go to Sales office, go to function TAB and assign multiple sales organizations there.

In the change form click New entry and assign the new sales organization and distribution channela and division combination.

You can assign as many combinations as needed here. 1. There are 2 version in CRM Org Model.

a) SBIV (Standard Backend Integration Version) b) EBIV (Enhanced Backend Integration Version)

2. EBIV is used to handle multiple assignments in CRM system.

3. As you know we have 3 Org Units as far as Sales is concerned i.e. Sales Org, Sales Office, Sales Group.

4. In R/3 there is a standard way to maintain multiple assignments among these org units. Ex: Sales Group 'X' works (assigned) for 2 Sales Offices 'North' and 'South'

simultaneously.

5. But in CRM this assignment is not as common as in R/3 and is not supported thru SBIV.

6. If you would like to have these multiple assignments made in R/3 available in CRM as well you may want to go thru EBIV.

7. Once you run EBIV you cannot go back to SBIV.

8. In EBIV divisions and distribution channels can only be assigned to sales units (sales organizations, sales offices, and sales groups). If they are assigned to any other neutral Org Units (Org Units without any Org Attributes), those assignments would be deleted once you shift from SBIV to EBIV.

What are the steps to create a sales order?

To create a standard sales order, proceed as follows:

In the initial screen, choose Logistics - Sales and distribution - Sales. Choose Order - Create (VA01).

(23)

Enter the order type and, if necessary, the organizational data.

The values for sales organization, for distribution channel and the division are usually proposed from user-defined parameters. Entries for the sales office and the sales group are optional.

The sales areas (sales organization, distribution channel, division) are derived from the sold-to or ship-to parties. This means that you do not have to enter the sales area when you create a sales document.

If you do not specify a sales area in the initial screen, the system uses the sold-to or ship-to parties, which you entered in the overview screen, ship-to derive the sales area.

If there are several sales areas for that particular sold-to or ship-to party, you can choose the right sales area in the following dialog box.

The system then copies the selected sales area into the entry screen. Choose Enter. Enter the following data:

- Sold-to party or ship-to party

If you only enter a ship-to party, the system uses this to determine the sold-to party and if necessary, the sales area. If there are several sold-to parties or sales areas for one ship-to party, a dialog box appears where you can choose the one you require.

An error message appears in the status bar to inform you if the system is not able to determine a sold-to party. If you enter a sold-to party that is also a unique ship-to party, the system automatically copies it as such and informs you in the status bar.

- Customer purchase order number - Material numbers

- Order quantities for the materials - Choose Enter.

If, for example, you defined several unloading points or several ship-to parties in the customer master record of the sold-to party, the system displays the alternatives in a dialog box. The system can display alternatives for any or all of the following data: – - Unloading point

- Ship-to party - Payer

- Bill-to party

Select the valid data from these proposals by positioning the cursor on the line and choosing Choose.

(24)

As soon as you have selected this data, the material data that you have entered is displayed.

If the system carries out an availability check and finds that there is insufficient stock for an order item to be delivered on the requested date, it displays a screen on which you can choose between several delivery proposals. You can find more information about this in Reactions to the Availability Check in Sales Documents. If you want to enter further data for the header or items, choose the corresponding menu entry. If you want to change data for the items, select the items before you choose a menu entry. Enter all necessary data. Save your document.

Duplicate customer purchase order

If you are facing a problem with duplicate customer purchase order as your company does not allowed a same customer purchase order with the same sales order type. You can activated the check for duplicate purchase order with "VOV8".

In the General Control Section, look for the field Check Purchase Order No and put

Default First Date is not Today

When end user created a new sales order with VA01, default First Date wasn't today, why?

Note:

1. Before today, default First Date was always today. 2. Nobody change system configuration.

Although you mention that nobody change the system configuration, it is very unlikely that the system will mis-behaved after one day.

Usually, after checking, you will find that someone have actually change the

configuration as it could not be a software bug since you have been using it for quite sometime without any problems.

The date is control by each Sales Order Type for each Sales Document type whether is it a

(25)

- OR - Standard Order, - RE - Returns etc.

Verify the Sales order type configuration with the following path:

IMG: Sales and Distribution --> Sales --> Sales Docs --> Sales Doc Hdr --> Define Sales Doc Types (transaction vov8) will let you control this by sales document type.

There is one field (Lead time in days) which "specify the number of days after the current date that the proposal for the requested delivery date in the sales document should be". This should be blank if you want the system to propose current day for delivery date.

SAP SD User Ticket:

Confirm quantity date is next day. I have created a sales order for 6 Tons.I have a stock of 10 Tons which is not reserved for any Sales order. I mean it is unrestricted stock. After creating sales order system should show as Doc date for confirming quantity for dispatch but it is showing the next day in the schedule line. What could be the reason?

The reason could be there should be processing times configured in the system

like..pick/pack times, transit time. Please check the shipping point and also the route for different lead times.

The other possibility could be holidays.

First check what the requested delivery date you have put in the order. Next check the lead times, for that you can go to the schedule line of the item and click on the

Procurement tab.

Check in OVLZ ---> In Pick/pack time wrkdys, any value is maintained there. For example, if 5 is given in this field, even if stock is available on the same day of order creation, system will allow to do PGI only after 5 days from the date of order created. Also go to VOV8, select your sale order type and check the Field "Lead Time in Days".

I'm using service material in my sales order and I need the schedule line to confirm the quantity always in the actual day (not depending on the delivery date).

T. Code: VOV8

(26)

In Tab: Shipping,

Check Box: Immediate Delivery (press F1 to read more about this functionality). Note: There are few more settings that you may check:

1. T. Code: OVLZ

Field: Pick/pack time wrkdys whether you have maintained any value. It should have been blank

2. T. Code: VOV8

Check how many days mentioned in Lead time in Days. If it is mentioned any days, remove it.

3. T. Code: OVZ9

Checked the Box: Check without RLT .

4. Check in material master MRP2 view how many days are maintained for the fields In-House production and GR Processing Time.

Auto proposed all the dates when creating Sales Order

How can I make the system auto create all the Sales Order date during creation?

Each Sales Order can have different date proposal settings.

Follows this step to set the default Sales Order Type proposal date:

- Goto VOV8, double click on sales order type.

- Look and tick the fields Propose delivery date and Propose PO date.

After making the necessary IMG changes, you need to input the Delivery Plant field for each Materials that you want the system to propose the default date.

To change the Materials field Delivery Plant:

Goto MM02, Select the View Sales: Sales Org. Data 1 and fill in the Delivery Plant.

(27)

Now, try creating a new sales order for the material and SAP will auto proposed all the dates in the sales order.

Define whether the Material can be used at which Sales and Distribution

process

Here you define how the system responds when entering a sales and distribution document

with this material in the differenet Sales and Distribution Process Flow..

You can use the material status, for example, to prevent orders from being entered for parts to be discontinued.

OR

To temporary block the creation of Sales Order for a certain materials.

Set the material status parameters in transaction SM30, Table Views V_TVMS. Click Maintain and double click into the Materials Status code.

You can set three types of reponse for each Sales and Distribution process :- 1. no dialog

2. warning when entering the document

3. error message (that is, the sales and distribution document cannot be entered on the basis of the material status)

Assign a Cost Center manually in a Sales Order

(VBAK-KOSTL)

The Cost Center Determination settings is in OVF3 - but there are some cases where the Cost Center must be exceptionally changed.

If the document category for order type in IMG VOV8 is defined to be "I" which belong to order type FD - Deliv.Free of Charge, then the field cost center is active for input during transaction VA01.

(28)

Alternatively, you can specify an order reason and assign a cost center to an order reason.

However the standard SAP works only at the header level though, so it would not work if cost center is needed on the line item.

The cost center are assign for such business transactions as : - Free deliveries

- Returns

- Deliveries of advertising materials

You can also make cost center allocation dependent on the order reason, for example: Order reason: Damage in transit

Order reason: Free sample

Both the IMG settings are done in transaction OVF3, either with/without the order reason.

Sales and Distribution - Transfer of

Requirements

The MRP department is informed about the quantities and deadlines by which incoming orders

should be delivered. The system checks the availability of the goods based on the requested

delivery date of the customer and creates MRP records which contain all necessary information

for passing on to planning. It ensures that the goods are available in time for the delivery.

Materials planning transfers the reported requirements and creates orders or purchase

requisitions from them etc.

For controlling transfer of requirements, you have to carry out the following steps:

1. Each requirement type has to be allocated to one requirement class only.

2. The transfer of requirements must be switched on at requirements class level, the sales

documents at schedule line level.

3. You must define a check group. It is possible to have this check group proposed for the

initial creation of a material master record.

4. Note that a plant must exist for transfer of requirements to be carried out at document

(29)

item level.

OVZG - Requirement class It specifies the following points:

- whether an availability check and a transfer of requirements is carried out for a

transaction (for sales documents, fine tuning using the schedule line category is possible),

- whether the requirements are relevant for MRP,

- the allocation indicator from the sales view which controls the settlement of customer

requirements with requirements

- whether an item is to be settled to an auxiliary account assignment, - the settlement profile,

- the results analysis key.

(Use transaction SM30 for V_* configuration)

OVZH - Requirements type

V_TVEPZ_V - Assignment of requirement type to Transaction

V_TVEP_V - Schedule line category

OVZ2 - Define Checking Group

V_TMVFU - Define the checking group that the system proposes when you create a new material

master record. You can overwrite the default value for the checking group in the

material master record.

Explain transfer of requirement? How it works and how to configure?

It specifies the following points:

1. Whether an availability check and a transfer of requirements is carried out for a

transaction (for sales documents, fine tuning using the schedule line category is possible), 2. Whether the requirements are relevant for MRP,

3. The allocation indicator from the sales view which controls the settlement of customer requirements with requirements,

4. Whether an item is to be settled to an auxiliary account assignment, 5. The settlement profile,

(30)

When a sales order is raised, then the system check for availability of goods. If the availability of goods is not there, then the system creates a TOR for the supply of goods to PP. Then PP can do procure or produce the goods. This can be configured by creating requirement class and requirement type and in the corresponding schedule line category requirement had to be checked.

The MRP department is informed about the quantities and deadlines by which incoming orders should be delivered. The system checks the availability of the goods based on the requested delivery date of the customer and creates MRP records which contain all necessary information for passing on to planning. It ensures that the goods are available in time for the delivery.

Materials planning transfers the reported requirements and creates orders or purchase requisitions from them etc.

The following sections on the transfer of requirements describe how to control the transfer of requirements.

The transfer of requirements is basically dependent upon the following factors: - requirements type

- requirement class - check group

- schedule line category

The transfer of requirements is controlled globally using the requirements class which is derived from the requirements type for all sales document types.

For the sales document types, fine tuning is also possible at schedule line level. This fine tuning is described in the section "Defining the procedure for each schedule line

category".

Note that the requirements classes are also used in production so you should coordinate any changes to the requirements classes with production. The requirements type and, eventually, requirements class are determined in the strategy group so all changes made there should also be coordinated with production.

For performing transfer of requirements, you have to carry out the following steps: 1. Each requirement type has to be allocated to one requirement class only.

2. The transfer of requirements must be switched on at requirements class level, the sales documents at schedule line level.

(31)

3. You must define a check group. It is possible to have this check group proposed for the initial creation of a material master record.

4. Note that a plant must exist for transfer of requirements to be carried out at document item level.

Requirements transferred to planning are further processed in the module MM. You must, therefore, coordinate the transfer of requirements with the module MM.

Define Tax Determination Rules

You specify the valid tax types in transaction OVK1. More than one tax type can be defined for a country by defining the sequence.

The SAP System determines the taxes automatically within pricing.

In the standard SAP R/3 System, the elements of tax calculation are predefined (for example, tax condition type "MWST" for taxes on sales and purchases).

Assign the plant for Tax Determination in OX10, using the country key, the SAP System recognizes which tax type is valid for a plant and thus which taxes are relevant when creating an SD document.

Define the Customer Taxes in OVK3, you will maintain the tax code in Customer Master. Define the Material Taxes in OVK4, which will then be maintain in Material Master. For example :-

MWST GST 0 Tax Exempt MWST GST 1 Liable for Taxes Now, you define the Tax Determination in VK12. VK12 - Domestic Taxes/Export Taxes

Condition Type MWST

Customer Taxes Material Taxes Rate Taxes 0 0 0 % 0 1 0 % 1 0 0 % 1 1 9 %

(32)

In this example, if both the Customer Master and Material Master Tax code is 1, Tax will be included when you create the Sales Order.

Tax Code in Customer Master / Sales Order

How can we maintain the Tax Code (Tax code - which we maintain in MWST Condtion Records) in Customer Master or in Sales Order?

There are few points which I would like to remind you:

1) MWST is a tax condition which is applied to customer to whom we are selling. The rate of tax is depend on various parameteres, whether is fully liable for tax or expemted (in case of Defence Customer)

2) There are few parameteres which we apply tax condition. Whether customer is tax liable? Whether material is tax exempted?

For example, if you are selling a goods which are free for tax to any customer, put the Tax Indicator (at MMR as '0'). If your

material is tax liable pur the Tax Indicator (at MMR as 1). If your customer is not liable for tax at all (like the case of Indian

Defence organisations) put the Tax Indicator (at CMR as 0) or 1 in case fully tax liable. 3) Now, at VK11 you need to mainatain your pricning conditions with all the

combinations like: 1 0

1 1 0 1 0 0

4) While maintaining your Material Master Records or Cusotmer Master Records, you must identify, which are tax liable and which are tax exempeted.

5) In anycase, as a SAP standard Best Practises, while processing a sales order, you must retrieve a Tax condition record from SAP database only and not entered Manually. Accordingly, at V/06, the MWST condition Defintions, the field for 'Manual Entries', it would be marked as - D (Not possible to process Manually).

Due to this setting, normally, you cannot maintain Condition tax code during sales order processing. And in Cusotmer Master, you can only maintain Tax Indicator and not Tax Code.

6) In case your client insists for Manual entry of Tax code during Sales Order processing, you can change the field at point 5) above to C-Manual entry is priority instead of D.

(33)

Taxation Explain with an example

I'm assuming that, the country is India and based on its requirement:

Sales tax is a state government revenue. There are two types of sales taxes, Local sales tax & central sales tax. Local sales tax is intra state whereas CST is inter state.

Example of LST : Point of sale i.e. delivering plant & ship to party are within the same state. The rates are defined by the respective state governments.

Example of CST : The Delivering plant & Ship to party geographic locations are 2 different states. At the point of sales from one state, the ST goes to that state govt. & consignment is despatched to the Ship to party. Once that consignment is received at the ship to party state, sales tax will be levied once the sales is registered there. For this case, the LST that is applicable by the Ship to party further will not be applicable in all

probability to be captured in SAP.

Stock transfer : This does not attract any sales tax. The consignment is transferred from one D plant to another D plant irrespective of inter/intra state sales. The invoice that is accompanied with the consignment thus shall not have any final value. It's a zero value invoice, but the basic prices needed to be mentioned.

The selling organisations normally needs to register with the sales tax authority of the respective state to have a warehouse or D plant to avoid the double taxation for their dealers/distributors.

Now, the pricing procedure that is there in 4.7 is Factory sale with formula-JFACT, in which the CST condition type is JIN1 & the LST is probably JIN2. There may be surcharge cond types as well which will calculate the amount on either JIN1 or JIN2. For config :

1.SPRO > S&D > Basic fn. > Pricing > Pricing control > Define & assign Pric. procedure > Maintain Pric proc.

2. The tax rates are normally driven from the Tax classification of Customer & Material access. To do this config, S&D >Basic fn. > Taxes. You need to include the condition type for country IN in 'Define tax determin rule'.

3. Same path : But go to Tax relevancy of master records where you configure the

condition type & options of rates that will flow to these masters. One needs to understand here properly as u need to have unique combinations for picking the sales tax rates. I will try to demonstrate the smallest example. Let's say, the LST rates are 2%,4% & 0%. I will have two options for material master here. 1 for taxable & 2 for not taxable.

(34)

For customer master, I will have 1-LST 2%, 2-LST4% & 3-LST0%. When I create master records for LST thru VK11 for JIN2, I will chose the access where the

combinations of customer & material tax classifications are available. If this access does not exist create it under an access sequence. But normally this is standard. The condition records will look like,

Cust-Tax classi. Material tax claasi. Rate Tax code 1 1 2% A1 2 1 4% A1 3 1 0% A1

Remember, rates are flown from the tax codes. Tax codes can be created thru T code FTXP. This is normally a FI job

SPRO

Material management Purchasing

Purchase order

Set up stock transport order Create checking rule

Scope of availability check

SPRO

Sales and distribution Basic functions

Availability check and transfer of requirements Availability check

Availability check with ATP planning or against planning Carry out control for availability check

Go to New Entries and define the scope of check in the combination of checking group and checking rule.

The following elements can be involved in the availability check

STOCKS:

[]Include safety stocks: Minimum stock at plant/ware house []Stock in transfer

[]Include quality inspection stock []Include

Inward movement Out ward movement Purchase orders Sales requirements Purchase requisitions Deliveries

Planned orders Release orders etc. Production orders

If we do not check the field [] ‘check without RLT’ the system considers RLT while checking the availability of the material

Note: Blocking the material for availability check

(35)

Availability check with ATP planning or against planning Define material block for other users

If we check the field Block [] during the availability check of a material the users cannot make changes in the Material Master, cannot create PO, cannot create sales orders.

Note: During the Material Master creation the system automatically proposes the checking group. Further the following setting is required.

SPRO

Availability check with ATP planning or against planning Define checking groups default values.

We need to assign the checking group to the combination of material type and plant.

Settlement Downpayment with Installment payment

Term

Scenario :- Problem with Down payment settlement using installment payment term. 1. When we create Sales order, (sales item value = 100) use payment term :

0009 (Installment Payment term, 30%, 40%, 30%). In the Billing Plan, I specify 2 records, 1st record is

Downpayment request 30% of Order value, billing type is FAZ . the 2nd record is Final invoice 100%, billing

type is F2.

2. Create Billing type Down payment request , it will document as Noted item in the accounting document.

3. Receive Downpayment from customer via FI screen , at this stage the asccounting document is created as following

Dr. Cash/Bank 30

Cr. Advance from customer 30

4. When I create Billing document for the sales item, the down payment value will be proposed for settlement at Billing

Creation, I then accept the default value of down payment clearing. The accounting document is as below

(36)

Dr. AR 30 (*split AR by installment payment term) AR 40

AR 30 Cr. Sales 100

Dr. Advance from customer 30 Cr. AR 9 (DP. 30% * 30) Cr AR 12 (DP. 30% * 40) Cr AR 9 (DP. 30% * 30)

It seems SAP settlement Down payment by Installment Payment term. I was wondering that is there are alternative or an option to setup the Down payment settlement

independent of Installment term. I meant, I don't want to have the last 3 Credit item as above, I want only 1 line item of credit, the accounting should be

Dr. AR 30 (*split AR by installment payment term) AR 40

AR 30 Cr. Sales 100

Dr. Advance from customer 30

Cr. AR 30 (Not separate by Installment payment term) Solutions : Suggesstions on how I could proceed?

Your problem with Down payment settlement is common. Many users object to the down payment or security lodgement mechanism. In our case we often park and apply the advance manually to final invoice.

However, following the above case we sometimes use this with our PS orders: 1. Create Sales order, (sales item value = 100) with billing plan with three steps 30% down payment,30% std billiing on

order completion and 70% on delivery. A little different to your original Billing Plan, but 1st record is Downpayment

request 30% of Order value, billing type is FAZ . the 2nd & 3rd records are std F2 invoices 30% ,70%.

2. Create Billing type Down payment request , it will document as Noted item in the accounting document.

3. Receive Downpayment from customer via FI screen , at this stage the accounting document is created as following :-

Dr. Cash/Bank 30

Cr. Security deposit payment 30 ( In many countries this may be subject to TAX laws)

4. Create the First Billing documents , the down payment value will be proposed for settlement at Billing Creation, then

(37)

accept the default value of down payment clearing as these equal each other. The accounting document is as below

Dr. AR 30 Cr. Sales 30

Dr. Advance from customer 30 Cr. AR 30

5. Create the Second Billing document ( down payment value has expired and will not be proposed) The accounting

document is as below is then standard for the last installement. Dr. AR 60

Cr. Sales 60

This alternative provides a cleaner option with the Downpayment.

Sales and Distribution - Upload Condition Pricing

RV14BTCI - Batch Input for Uploading Condition Pricing

After executing the program, you have to use SM35 to process the update program. Envirionment : 4.6x

Require flat file :- ROW 1 BGR00 ROW 2 BKOND1

ROW 3 BKOND2 - no scale ROW 4 BKOND2 - no scale ROW 5 BKOND3 - with scale ROW 6 BKOND2 - no scale

Sample flat file for uploading table A305 - Customer/Material with release status :- 0BIPRICE 123SAPABAP X 1VK15 A305V PR00 2ALL 990000123456SAP8204142100 2002043020020401 50USD 100PC 2ALL 990000123456SAP8217168100 2002043020020401 50USD 100PC 3 100PC 2 3 200PC 1 2ALL 990000123456SAP8220133910

(38)

There a total of 4 flat file format :-BGR00 - Session Header Record

---| Field name ---| Description ---| Report header ---| Cat. ---| Length | Dec. |

---| STYPE ---| Record type ---| 0 ---| CHAR ---| 000001 | 000000 |

| NODATA | No batch input | / | CHAR | 000001 | 000000 |

---BKOND1 - Header Record

(39)

| KVEWE | Usage | U | CHAR | 000001 | 000000 |

---BKOND2 - Main Data Record

(40)

| KMEIN | | | CHAR | 000003 | 000000 |

| MWSK1 | Tax code | Tx | CHAR | 000002 | 000000 |

| KONMS | Scale UoM | UoM | UNIT | 000003 | 000000 |

| STFKZ | Scale type | S | CHAR | 000001 | 000000 |

| LOEVM_KO | Deletion indic. | D | CHAR | 000001 | 000000 |

---BKOND3 - Scale Data Record

| KONMS | Scale UoM | UoM | UNIT | 000003 | 000000 |

(41)

---

Sales Order Changed History Display

*

* Sales Order Changed History Display *

* You can execute the report by : * 1. Change Date

* 2. User Name

* 3. Sales Order Number *

* Submitted by : SAP Basis, ABAP Programming and Other IMG Stuff * http://www.sap-img.com

*

REPORT ZSDCHANGE LINE-SIZE 132 NO STANDARD PAGE HEADING LINE-COUNT 065(001) MESSAGE-ID VR. TABLES: DD04T, CDHDR, CDPOS, DD03L, DD41V, T685T, VBPA, TPART, KONVC, VBUK.

DATA: BEGIN OF ICDHDR OCCURS 50. INCLUDE STRUCTURE CDHDR. DATA: END OF ICDHDR.

SELECT-OPTIONS: XUDATE FOR ICDHDR-UDATE, XNAME FOR ICDHDR-USERNAME, XVBELN FOR VBUK-VBELN. SELECTION-SCREEN SKIP.

SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-001. PARAMETERS: SUDATE RADIOBUTTON GROUP R1,

SNAME RADIOBUTTON GROUP R1, SOBID RADIOBUTTON GROUP R1. SELECTION-SCREEN END OF BLOCK BLK1. DATA: WFLAG,

WCHANGENR LIKE CDHDR-CHANGENR, WUDATE LIKE CDHDR-UDATE,

WNAME LIKE CDHDR-USERNAME, WVBELN LIKE VBUK-VBELN, WDEC1 TYPE P DECIMALS 3, WDEC2 TYPE P DECIMALS 3,

(42)

WDEC3 TYPE P DECIMALS 3, WDEC4 TYPE P DECIMALS 3.

DATA: UTEXT(16) VALUE 'has been changed', ITEXT(16) VALUE 'has been created', DTEXT(16) VALUE 'has been deleted'. DATA: BEGIN OF ICDSHW OCCURS 50.

INCLUDE STRUCTURE CDSHW. DATA: END OF ICDSHW.

DATA: BEGIN OF ITAB OCCURS 10. INCLUDE STRUCTURE CDSHW. DATA: UDATE LIKE CDHDR-UDATE,

USERNAME LIKE CDHDR-USERNAME, CHANGENR LIKE CDHDR-CHANGENR, VBELN(10),

POSNR(6), ETENR(4), INDTEXT(200), END OF ITAB.

SELECT * FROM VBUK WHERE VBELN IN XVBELN. CLEAR CDHDR. CLEAR CDPOS. CDHDR-OBJECTCLAS = 'VERKBELEG'. CDHDR-OBJECTID = VBUK-VBELN. PERFORM READHEADER. PERFORM READPOS. LOOP AT ITAB. CASE ITAB-TABNAME. WHEN 'VBPA'. IF ITAB-FNAME = 'KUNNR' OR ITAB-FNAME = 'LIFNR' OR ITAB-FNAME = 'PARNR' OR ITAB-FNAME = 'PERNR' OR ITAB-FNAME IS INITIAL. MOVE ITAB-TABKEY TO VBPA.

SELECT SINGLE * FROM TPART WHERE SPRAS = SY-LANGU AND PARVW = VBPA-PARVW. IF SY-SUBRC = 0.

REPLACE '&' WITH TPART-VTEXT INTO ITAB-INDTEXT. ENDIF.

ENDIF. WHEN 'VBAP'.

IF ITAB-FNAME IS INITIAL.

REPLACE '&' WITH 'Item' INTO ITAB-INDTEXT. ENDIF.

WHEN 'KONVC'.

MOVE ITAB-TABKEY TO KONVC.

SELECT SINGLE * FROM T685T WHERE SPRAS = SY-LANGU AND KVEWE = 'A'

AND KAPPL = 'V'

AND KSCHL = KONVC-KSCHL. IF SY-SUBRC = 0.

REPLACE '&' WITH T685T-VTEXT INTO ITAB-INDTEXT. ENDIF.

(43)

ENDCASE.

IF ITAB-INDTEXT(1) EQ '&'.

REPLACE '&' WITH ITAB-FTEXT(40) INTO ITAB-INDTEXT. ENDIF.

IF ITAB-CHNGIND = 'I'.

REPLACE '%' WITH ITEXT INTO ITAB-INDTEXT. ELSEIF ITAB-CHNGIND = 'U'.

REPLACE '%' WITH UTEXT INTO ITAB-INDTEXT. ELSE.

REPLACE '%' WITH DTEXT INTO ITAB-INDTEXT. ENDIF. CONDENSE ITAB-INDTEXT. MODIFY ITAB. ENDLOOP. ENDSELECT. IF SUDATE = 'X'.

SORT ITAB BY UDATE VBELN POSNR ETENR. ELSEIF SOBID = 'X'.

SORT ITAB BY VBELN POSNR ETENR UDATE. ELSE.

SORT ITAB BY USERNAME VBELN POSNR ETENR UDATE. ENDIF. LOOP AT ITAB. CLEAR WFLAG. IF SUDATE = 'X'. IF WUDATE NE ITAB-UDATE. SKIP. WRITE:/001 ITAB-UDATE, 023 ITAB-USERNAME, 037(10) ITAB-VBELN. WFLAG = 'X'. WUDATE = ITAB-UDATE. WCHANGENR = ITAB-CHANGENR. ENDIF. ELSEIF SOBID NE 'X'. IF WVBELN NE ITAB-VBELN. SKIP. WRITE:/001 ITAB-VBELN. WVBELN = ITAB-VBELN. ENDIF. ELSE. IF WNAME NE ITAB-USERNAME. SKIP. WRITE:/001 ITAB-USERNAME. WNAME = ITAB-USERNAME. ENDIF. ENDIF. IF WCHANGENR NE ITAB-CHANGENR. WRITE:/023 ITAB-USERNAME, 037(10) ITAB-VBELN. WFLAG = 'X'. WCHANGENR = ITAB-CHANGENR. ENDIF. IF WFLAG = 'X'. WRITE: 013 ITAB-CHNGIND,