SAP T Codes

SAP Functional Transaction Codes Customer
XD01 Create Customer (Centrally)
XD02 Change Customer (Centrally)
XD03 Display Customer (Centrally)
XD04 Customer Changes (Centrally)
XD05 Block customer (centrally)
XD06 Mark customer for deletion (centr.)
XD07 Change Customer Account Group
XD99 Customer master mass maintenance
XDN1 Maintain Number Ranges (Customer)
Vendor
XEIP Number range maintenance: EXPIMP
XK01 Create vendor (centrally)
XK02 Change vendor (centrally)
XK03 Display vendor (centrally)
XK04 Vendor Changes (Centrally)
XK05 Block Vendor (Centrally)
XK06 Mark vendor for deletion (centrally)
XK07 Change vendor account group
Sales Order
VA00 Initial Sales Menu
VA01 Create Sales Order
VA02 Change Sales Order
VA03 Display Sales Order
VA05 List of Sales Orders
VA07 Compare Sales - Purchasing (Order)
VA08 Compare Sales - Purchasing (Org.Dt.)
Inquiry
VA11 Create Inquiry
VA12 Change Inquiry
VA13 Display Inquiry
VA14L Sales Documents Blocked for Delivery
VA15 Inquiries List
Quotation
VA21 Create Quotation
VA22 Change Quotation
VA23 Display Quotation
VA25 Quotations List
VA26 Collective Processing for Quotations
Contract
VA41 Create Contract
VA42 Change Contract
VA42W Workflow for master contract
VA43 Display Contract
VA44 Actual Overhead: Sales Order
VA45 List of Contracts
VA46 Coll.Subseq.Processing f.Contracts
Item Proposal
VA51 Create Item Proposal
VA52 Change Item Proposal
VA53 Display Item Proposal
VA55 List of Item Proposals
VA88 Actual Settlement: Sales Orders
Delivery (Outbound)
VL00 Shipping
VL01 Create Delivery
VL01N Create Outbound Dlv. with Order Ref.
VL01NO Create Outbound Dlv. w/o Order Ref.
VL02 Change Outbound Delivery
VL02N Change Outbound Delivery
VL03 Display Outbound Delivery
VL03N Display Outbound Delivery
VL04 Process Delivery Due List
VL06 Delivery Monitor
VL06C List Outbound Dlvs for Confirmation
VL06D Outbound Deliveries for Distribution
VL06F General delivery list - Outb.deliv.
VL06G List of Oubound Dlvs for Goods Issue
VL06I Inbound Delivery Monitor
VL06IC Confirmation of putaway inb. deliv.
VL06ID Inbound Deliveries for Distribution
VL06IF Selection inbound deliveries
VL06IG Inbound deliveries for goods receipt
VL06IP Inbound deliveries for putaway
VL06L Outbound Deliveries to be Loaded
VL06O Outbound Delivery Monitor
VL06P List of Outbound Dlvs for Picking
VL06T List Outbound Dlvs (Trans. Planning)
VL06U List of Uncheckd Outbound Deliveries
VL08 Confirmation of Picking Request
VL09 Cancel Goods Issue for Delivery Note
VL10 Edit User-specific Delivery List
VL10A Sales Orders Due for Delivery
VL10B Purchase Orders Due for Delivery
Customer management
FD01 Create Customer (Accounting)
FD02 Change Customer (Accounting)
FD02CORE Maintain customer
FD03 Display Customer (Accounting)
FD04 Customer Changes (Accounting)
FD05 Block Customer (Accounting)
FD06 Mark Customer for Deletion (Acctng)
FD08 Confirm Customer Individually(Actng)
FD09 Confirm Customer List (Accounting)
FD10 Customer Account Balance
FD10N Customer Balance Display
FD10NA Customer Bal. Display with Worklist
FD10NET Customer Balance Display
FD11 Customer Account Analysis
FD15 Transfer customer changes: send
FD16 Transfer customer changes: receive
FD24 Credit Limit Changes
FD32 Change Customer Credit Management
FD33 Display Customer Credit Management
FD37 Credit Management Mass Change
Pricing
V/03 Create Condition Table (SD Price)
V/04 Change Condition Table (Sales pr.)
V/05 Display Condition Table: (Sales Pr.)
V/06 Condition Categories: SD Pricing
V/07 Maintain Access (Sales Price)
V/08 Conditions: Procedure for A V
V/09 Condition Types: Account Determin.
V/10 Account Determination: Access Seqnc
V/11 Conditions: Account Determin.Proced.
V/12 Account Determination: Create Table
V/13 Account Determination: Change Table
V/14 Account Determination: Display Table
BOM
CS00 BOM Menu
CS01 Create Material BOM
CS02 Change Material BOM
CS03 Display Material BOM
CS05 Change Material BOM Group
CS06 Display Material BOM Group
CS07 Allocate Material BOM to Plant
CS08 Change Material BOM - Plant Alloc.
CS09 Display Allocations to Plant
CS11 Display BOM Level by Level
CS12 Multilevel BOM
CS13 Summarized BOM
CS14 BOM Comparison
CS15 Single-Level Where-Used List
CS20 Mass Change: Initial Screen
CS21 Mass Material Change: Initial Screen
CS22 Mass Document Change: Initial Screen
CS23 Mass Class Change: Initial Screen
CS25 Archiving for BOMs
CS26 BOM deletion
CS27 Retrieval of BOMs
CS28 Archiving for BOMs
CS31 Create class BOM
CS32 Change class BOM
CS33 Display class BOM
CS40 Create Link to Configurable Material
CS41 Change Material Config. Allocation
CS42 Display Material Config. Assignment
CS51 Create standard BOM
CS52 Change standard BOM
CS53 Display standard BOM
CS61 Create Order BOM
CS62 Change Order BOM
CS63 Display Order BOM
CS71 Create WBS BOM
CS72 Change WBS BOM
CS73 Display WBS BOM
CS74 Create multi-level WBS BOM
CS75 Change multi-level WBS BOM
CS76 Display multi-level WBS BOM
CS80 Change Documents for Material BOM
CS81 Change Documents for Standard BOM
CS82 Change documents for sales order BOM
CS83 Change documents for WBS BOM
CS84 Change documents for class BOM
CS90 Material BOM Number Ranges
CS91 Number Ranges for Standard BOMs
CS92 Number Ranges for Sales Order BOMs

You can also refer these codes

V+01 Create Sales Call
V+02 Create Telephone Call
V+03 Create Sales Letter
V+11 Create Direct Mailing
V+21 Create Sales Prospect
V+22 Create Competitor
V+23 Create Business Partner
V-01 Create Sales Order
V-02 Create Quotation
V-03 Create ordering party (Sales)
V-09 Create ordering party (Centrally)
V-11 Create carrier
V-12 Create Customer Hierarchy Nodes
V-31 Create Freight 1
V-32 Create Freight 1 with Reference
V-33 Change Freight 1
V-34 Create Freight 1
V-35 Create Freight 1
V-36 Create Freight 1 with Reference
V-37 Change Freight 2
V-38 Display Freight 2
V-41 Create Material Price
V-42 Create Material Price w/ref.
V-43 Change Material Price
V-44 Display Material Price
V-45 Create Price List
V-46 Create Price List w/ref.
V-47 Change Price List
V-48 Display Price List
V-49 Create Customer-Specific Price
V-50 Create Customer-spec. Price w/ref.
V-51 Change Cust.price
V-52 Display Cust.price
V-61 Create Cust.disc./surcharge
V-62 Create Customer Disc/Surch. w/ref
V-63 Change Cust.Disc/Surcharge
V-64 Display Cust.Disc/Surcharge
V-65 Create Mat.Disc/Surcharge
V-66 Create w/ref.Material Disc/Surcharge
V-67 Change Mat.Disc/Surcharge
V-68 Display Mat.Disc/Surcharge
V-69 Create Price grp Disc/Surch.
V-70 Create w/ref.Price Group Disc/Surch.
V-71 Change Price grp Disc/Surch.
V-72 Display Price grp Disc/Surch.
V-73 Create Mat.pr.grp Disc/Surch
V-74 Create w/ref.Mat.pr.grp Disc/Surch
V-75 Change Mat.pr.grp Disc/Surch
V-76 Display Mat.pr.grp Disc/Surch
V-77 Create Cust/MatPrGrp Disc/Su
V-78 Create w/ref.Cust/MatPrGrp Disc/Surc
V-79 Change Cust/MatPrGrp Disc/Su
V-80 Display Cust/MatPrGrp Disc/Su
V-81 Create Cust/mat.Disc/Surch.
V-82 Create w/ref.Cust/Mat.Disc/Surcharge
V-83 Change Cust/mat.Disc/Surch.
V-84 Display Cust/mat.Disc/Surch.
V-85 Create PGrp/MPrGrp Disc/Surc
V-86 Create w/ref.PrGrp/MatPrGrp Disc/Sur
V-87 Change PGrp/MPrGrp Disc/Surc
V-88 Display PGrp/MPrGrp Disc/Surc
V-89 Create PGrp/MPrGrp Disc/Surc
V-90 Create w/ref.PrGrp/Mat Disc/Surch.
V-91 Change PGrp/mat Disc/Surch.
V-92 Display PGrp/mat.Disc/Surch.
V.00 List of Incomplete Documents
V.01 Sales Order Error Log
V.02 List of Incomplete Sales Orders
V.03 List of Incomplete Inquiries
V.04 List of Incomplete Quotations
V.05 List of Incomplete Sched.Agreements
V.06 List of Incomplete Contracts
V.07 Periodic billing
V.14 Sales Orders Blocked for Delivery
V.15 Display Backorders
V.21 Log of Collective Run
V.22 Display Collective Runs
V.23 Release Orders for Billing
V.24 Display Work List for Invoice Lists
V.25 Release Customer Expected Price
V.26 Selection by Object Status
V/03 Create Condition Table (SD Price)
V/11 Conditions: Account Determin.Proced.
V/21 View V_TVSA_NAC
V/22 View V_TVTY_NAC
V/23 View V_TVST_KOM
V/I5 Condit: Pricing SD - Index in Backgr
V/I6 Display conditions using index
V/LD Execute pricing report
V101 Initial Sales Menu
V12L_A Create Pricing Report
V12L_B Change Pricing Report
V12L_C Display Pricing Report
V23 Sales Documents Blocked for Billing
VA01 Create Sales Order
VA02 Change Sales Order
VA03 Display Sales Order
VA05 List of Sales Orders
VA07 Compare Sales - Purchasing (Order)
VA08 Compare Sales - Purchasing (Org.Dt.)
VA11 Create Inquiry
VA12 Change Inquiry
VA13 Display Inquiry
VA14L Sales Documents Blocked for Delivery
VA15 Inquiries List
VA21 Create Quotation
VA22 Change Quotation
VA23 Display Quotation
VA25 Quotations List
VA26 Collective Processing for Quotations
VA31 Create Scheduling Agreement
VA32 Change Scheduling Agreement
VA33 Display Scheduling Agreement
VA35 List of Scheduling Agreements
VA41 Create Contract
VA42 Change Contract
VA43 Display Contract
VA44 Actual Overhead: Sales Order
VA45 List of Contracts
VA46 Coll.Subseq.Processing f.Contracts
VA51 Create Item Proposal
VA52 Change Item Proposal
VA53 Display Item Proposal
VA55 List of Item Proposals
VA88 Actual Settlement: Sales Orders
VA94 Load Commodity Codes for Japan
VACF Commit. carried forwrd: Sales orders
VAM4 Merge: Japan - Commodity Code
VAN1 Actual Reval.: Sales Order
VAP1 Create Contact Person
VAP2 Change Contact Person
VAP3 Display Contact Person
VARA Archiving
VARK Archiving
VARR Archiving
VASK Deleting Groups
VB(7 Rebate Agreement Settlement
VB(8 List Rebate Agreements
VB(D Rebate Agreement Settlement
VB01 Create Material Listing/Exclusion
VB02 Change Material Listing/Exclusion
VB03 Display Material Listing/Exclusion
VB11 Create Material Substitution
VB12 Change Material Substitution
VB13 Display Material Substitution
VB14 Reference Material Substitution
VB21 Create Sales Deal
VB22 Change Sales Deal
VB23 Display Sales Promotion
VB25 List of Sales Deals
VB31 Create Promotion
VB32 Change Promotion
VB33 Display Promotion
VB35 Promotions List
VB41 Create cross-selling
VB42 Change cross-selling
VB43 Display cross-selling
VB44 Copy cross-selling
VBG1 Create Material Grouping
VBG2 Change Material Grouping
VBG3 Display Material Grouping
VBK1 Create Bonus Buy
VBK2 Change Bonus Buy
VBK3 Display Bonus Buy
VBK6 Delete Bonus Buy
VBN1 Free goods - Create (SD)
VBN2 Free goods - Change (SD)
VBN3 Free goods - Display (SD)
VBO1 Create Rebate Agreement
VBO2 Change Rebate Agreement
VBO3 Display Rebate Agreement
VBOF Rebate: Update Billing Documents
VC/2 Customer Master Data Sheet
VC01 Create Sales Activity
VC010102 Only Follow-up Activities
VC010103 Do not Delete Mail. Camp.+Addresses
VC01N Edit Sales Activity
VC01N_M Edit Mailing
VC02 Change Sales Activity
VC03 Display Sales Activity
VC05 Sales support monitor
VC06 Parallel Processing for Address List
VC10 Report Tree - Select Addresses
VC15 Crossmatching
VCAR Archiving
VCC1 Payment Cards: Worklist
VCH1 Create Batch Search Strategy
VCH2 Change Batch Search Strategy
VCH3 Display Batch Search Strategy
VCR1 Competitive products
VCUN Reload
VD01 Create Customer (Sales)
VD02 Change Customer (Sales)
VD03 Display Customer (Sales)
VD04 Customer Changes (SD)
VD05 Block customer (sales)
VD06 Mark customer for deletion (sales)
VD07 Ref. doc. det. for ref. customer
VD51 Maintain Customer-Material Info
VD52 Maintain Cust-Mat.Info w/Select.Scrn
VD53 Display Customer-Material Info
VD54 Display Customer-Material Info
VD59 List customer-material-info
VDDI EMU currency conversion cust. master
VDH1 Customer Hierarchy Maintenance (SD)
VDH1N Display/Maintain Customer Hierarchy
VDH2 Display Customer Hierarchy
VDH2N Display customer hierarchy
VE01 INTRASTAT: Selection Dispatch to EU
VE02 INTRASTAT: Create Form - Germany
VE03 INTRASTAT: Create File - Germany
VE04 EXTRASTAT: Data selection for export
VE05 EXTRASTAT: Create File - Germany
VE06 INTRASTAT: Paper Form - Belgien
VE07 Create INTRASTAT Form for France
VE08 Create INTRASTAT File for Italy
VE09 Create INTRASTAT file for Belgium
VE10 Create INTRASTAT file for Holland
VE11 Create INTRASTAT file for Spain
VE12 Create INTRASTAT form for Holland
VE13 KOBRA data selection: export Germany
VE14 Create KOBRA file for Germany
VE15 Create disk - INTRA/EXTRA/KOBRA/VAR
VE16 Create INTRASTAT form for Austria
VE17 Create INTRASTAT form for Sweden
VE18 SED data selection for USA exporters
VE19 Create SED form for USA
VE20 Create AERP file for USA
VE21 VAR: Selection of bill. docs Switz.
VE22 Create VAR form for Switzerland
VE23 V.A.R.: File - Switzerland
VE24 Comm. Code Number Information (old)
VE25 SED: Selection: USA Carriers
VE27 HMF: Selection - USA
VE29 Assigned Documents for Each License
VE30 Existing licenses
VE31 Blocked SD Documents
VE32 INTRASTAT: Paper Form - Ireland
VE33 INTRASTAT: Paper Form - U.K.
VE37 INTRASTAT: File - France
VE42 INTRASTAT: File - Denmark
VE45 INTRASTAT: Paper Form - Greece
VE46 INTRASTAT: File - Finland
VE54 Preference Determination: Collective
VE55 Preference Determination: Individual
VE56 Check Export Control for Consistency
VE64 Commodity Code/Customs Areas
VE65 Preference Reg./Percentage Rates
VE66 Preference Procedure
VE67 Aggregate Vendor Declarations
VE68 Request Vendor Declarations
VE73 Goods Catalog: Create Document
VE74 Goods Catalog: Create Diskette
VE81 Check Report: General FT Data
VE82 Check Report: Export Control Data
VE83 Check Report: Preference Data
VE84 Monitoring: Purchasing Info Records
VE85 Change Statistical Value - Import
VE86 Display Statistical Value - Import
VE87 Change Stat.Value - Subcontracting
VE88 Change Statistical Value - Export
VE89 Display Statistical Value - Export
VE90 Change preference values
VE91 Display Preference Values
VE94 Load Commodity Code for EU Countries
VE95 Create INTRASTAT papers: Portugal
VE96 EXTRASTAT Data Select.: Init. Screen
VE97 Create EXTRASTAT tape: Netherlands
VEB5 Calculate Assemblies Individually
VEB6 Calculate Assemblies Collectively
VECZ INTRASTAT: File - Czech Republic
VEFU Foreign Trade: Add INTRASTAT Data
VEHU INTRASTAT: File - Hungary
VEI0 Create INTRASTAT CUSDEC EDI IE
VEI3 Display Stat.Value - Subcontracting
VEI4 Merge: Remaining Commodity Codes
VEI7 Create INTRASTAT CUSDEC EDI GB
VEI8 Create INTRASTAT CUSDEC EDI AT
VEI9 Create INTRASTAT CUSDEC EDI ES
VEIA Create INTRASTAT CUSDEC EDI SE
VEIAE EXTRASTAT Archiving
VEIAI INTRASTAT Archiving
VEIB Create INTRASTAT CUSDEC EDI PT
VEID Create INTRASTAT CUSDEC EDI LU
VEIE SAPMSED8: Call EXPINV02
VEII SAPMSED8: Call IMPINV01
VEM4 Merge: EU - Commodity Code
VEPL Create INTRASTAT CUSDEC EDI PL
VEPR Customs log
VESK Create INTRASTAT CUSDEC EDI SK
VEU4 Load Commodity Code-Other Countries
VEXU Foreign Trade: Add EXTRASTAT Data
VF01 Create Billing Document
VF02 Change Billing Document
VF03 Display Billing Document
VF04 Maintain Billing Due List
VF05 List Billing Documents
VF06 Batch billing
VF07 Display bill. document from archive
VF11 Cancel Billing Document
VF21 Create Invoice List
VF22 Change invoice list
VF23 Display Invoice List
VF24 Edit Work List for Invoice Lists
VF25 List of Invoice Lists
VF26 Cancellation invoice list
VF27 Display invoice list from archive
VF31 Output from Billing Documents
VF44 Revenue Recognition: Worklist
VF45 Revenue recognition: Revenue report
VF46 Revenue Recognition: Cancellation
VF48 Revenue Recognition: Compare Report
VFP1 Set Billing Date
VFRB Retro-billing
VFX3 List Blocked Billing Documents
VG01 Create Group
VG02 Change Group
VG03 Display Group
VGM1 Create Group for Freight List
VGM2 Change Group for Freight List
VGM3 Display Group for Freight List
VI01 Create shipment costs
VI02 Change shipment costs
VI03 Display shipment costs
VI04 Create shipment cost worklist
VI05 Change shipment cost worklist
VI06 Collective run in background
VI07 Collective run in background
VI08X Display FT data in purchasing doc.
VI09X Change FT Data in Purchasing Doc.
VI10X Display FT Data in Billing Document
VI11 List shipment costs: Calculation
VI12 List shipment costs: Settlement
VI14X Change FT Data in Billing Document
VI16 Logs for worklist shipment
VI18 Display Anti-dumping
VI19 Display Third-country Customs Duties
VI20 Display Customs Quota
VI21 Display Pharmaceutical Products
VI22 Display Customs Exemption
VI23 Display Preferential Customs Duties
VI24 Code Number Information - Import
VI25 Display Gross Price - Customs
VI26 Display Surcharge/Discount - Customs
VI27 Display Freight - Customs
VI54 Customs Approval Numbers
VI55 Approval Number per Plant
VI64X Display FT Data in Outbound Delivery
VI72 Display Insurance - Customs
VI73N Maintain Vendor Declaration
VI74N Display Vendor Declaration
VI75 Vendor Declarations - Dunning notice
VI77X Change FT Data in Outbound Delivery
VI78 Foreign Trade: Country Data
VI79X Display FT Data in Goods Receipt
VI80X Change FT Data in Goods Receipt
VI81 Check Report: CAP Products
VI82 Check General Customer Master Data
VI83 Check Customer Master/Legal Control
VI84 Doc.Payments: Check Customer Master
VI85 Incompleteness: Foreign Trade Vendor
VI86 Incompleteness: Cross-plant
VI94 Load Import Code Nos - EU Countries
VI98 Receipt-Basis for Intercomp.Billing
VI99 Returns and Credit Memos
VIB3 Foreign Trade Output Status
VIB4 Print Transaction: Initial Procg
VIB5 Print Transaction: Repeat Procg
VIB6 Print Transaction: Error in Procg
VIB7 Send IDoc Output - Initial Procg
VIB8 Send IDoc Output - Repeat Procg
VIB9 Send IDoc Output - Error in Procg
VIBA Send IDoc Output-AES-Initial Procg
VIBB Send IDoc Output-AES-Repeat Procg
VIBC Send IDoc Output-AES-Error in Procg
VIEX FT: Journal Export Actual
VII4 Merge: Rest - Import Code Number
VIIM FT: Op. Cockpit: Purchase order
VIJ1 Journal Import
VIJ2 Journal Export
VIM4 Merge: EU - Import Code Number
VIMM Decl. Recpts/Disptch Min. Oil Prod.
VIS3 Check program: Cross-plant
VIU4 Load Import Code No.-Other Countries
VIWE FT: Op. Cockpit: Goods Receipt
VJ01 In-Force Bus. Groups Pension Funds
VJ02 Insurance Type
VJ03 Customer type
VJ11 Insurance Class: Reporting
VK01 Conditions: Dialog Box for CondElem.
VK03 Create Condition Table
VK11 Create Condition
VK12 Change Condition
VK13 Display Condition
VK14 Create Condition with Reference
VK30 Maintain Variant Conditions
VK31 Condition Maintenance: Create
VK32 Condition Maintenance: Change
VK33 Condition Maintenance: Display
VK34 Condition Maint.: Create with Refer.
VKA1 Archiving conditions
VKA2 Deleting conditions
VKA3 Reloading conditions
VKA4 Archiving agreements
VKA5 Deleting agreements
VKA6 Reloading agreements
VKM1 Blocked SD Documents
VKM2 Released SD Documents
VKM3 Sales Documents
VKM4 SD Documents
VKM5 Deliveries
VKP1 Sales price calculation
VKP2 Display POS Conditions
VKP3 Pricing document for material
VKP4 Pricing document for org. structure
VKP5 Create Calculation
VKP6 Change pricing document
VKP7 Display pricing document
VKP8 Display Price Calculation
VKPA Archiving
VKPB Sales price calc. in background run
VKPR Read archive file
VKU2 Total Revaluation at Retail
VKU3 Partial Revaluation at Retail
VKU4 Rtl Revaluation Docs for Material
VKU6 Report: List Crtn for Rtl Pr. Change
VKU7 Report: Total Reval. for Rtl Pr. Chn
VKUN Reload
VL01 Create Delivery
VL01N Create Outbound Dlv. with Order Ref.
VL01NO Create Outbound Dlv. w/o Order Ref.
VL02 Change Outbound Delivery
VL02N Change Outbound Delivery
VL03 Display Outbound Delivery
VL03N Display Outbound Delivery
VL04 Process Delivery Due List
VL06 Delivery Monitor
VL06C List Outbound Dlvs for Confirmation
VL06F General delivery list - Outb.deliv.
VL06G List of Oubound Dlvs for Goods Issue
VL06I Inbound Delivery Monitor
VL06IC Confirmation of putaway inb. deliv.
VL06IG Inbound deliveries for goods receipt
VL06IP Inbound deliveries for putaway
VL06L Outbound Deliveries to be Loaded
VL06O Outbound Delivery Monitor
VL06P List of Outbound Dlvs for Picking
VL06T List Outbound Dlvs (Trans. Planning)
VL06U List of Uncheckd Outbound Deliveries
VL09 Cancel Goods Issue for Delivery Note
VL10 Edit User-specific Delivery List
VL10A Sales Orders Due for Delivery
VL10B Purchase Orders Due for Delivery
VL10BATCH VL10 Background planning
VL10C Order Items Due for Delivery
VL10D Purch. Order Items due for Delivery
VL10E Order Schedule Lines due for Deliv.
VL10F PurchOrd Schedule Lines due for Dlv.
VL10G Documents due for Delivery
VL10H Items Due for Delivery
VL10I Schedule Lines due for Delivery
VL10U Cross-System Deliveries
VL10UC Check / combine unchecked deliveries
VL21 Post goods issue in background
VL22 Display Delivery Change Documents
VL23 Goods Issue (Background Processing)
VL31N Create Inbound Delivery
VL32N Change Inbound Delivery
VL33N Display Inbound Delivery
VL34 Worklist Inbound Deliveries
VL35 Create Wave Picks: Delivery/Time
VL35_S Create Wave Picks: Shipment
VL35_ST Create Wave Picks: Shipment/Time
VL36 Change Picking Waves
VL37 Wave Pick Monitor
VL38 Groups Created: Wave Picks
VL51 Create Route Schedule: Initial Scr.
VL52 Change Route Schedule: Initial Scr.
VL53 Display Route Schedule: Initial Scr.
VL60 Extended Inbound Delivery Processing
VL60C Clearing
VL60P Posting
VL60V Edit Document
VL64 Worklist Inbound Deliveries
VL65 Inbound Delivery Purge Report
VL66 Inbound Delivery Delete Report
VL71 Output from Outbound Deliveries
VL72 Output from Groups of Deliveries
VL74 Output from Handling Units
VL75 Shipping Notification Output
VLLA RWE: Picking/Goods Issue Analysis
VLLC RWE: Archive Data
VLLE RWE: Goods Receipt/Putaway Analysis
VLLG RWE: Analyze Complete Overview
VLLP Rough Workload Forecast: Display Log
VLLQ RWE: Returns to Vendor Analysis
VLLR RWE: Customer/Store Return Analysis
VLMOVE HU Goods Movements
VLPOD POD - Change Outbound Delivery
VLPODA POD - Display Outbound Delivery
VLPODF Worklist: POD Subsequent Processing
VLPODL Worklist: POD Deliveries
VLPODQ Automatic PoD Confirmation
VLSP Subsequent Outbound-Delivery Split
VLSPS Outbound Delivery Split via HU Scan
VM01 Create Hazardous Material
VM02 Change Hazardous Material
VM03 Display Hazardous Material
VN01 Number Assignment for SD Documents
VN03 Number Assignment for Doc.Conditions
VNPU Partner Conversion
VOB3 Comparison: Bill. Docs and Stats
VOEX Incompleteness: Billing Document
VOIM Incompleteness: Purchase Order
VOLI Incompleteness: Delivery
VOWE Incompleteness: Goods Receipt
VP01 Maintain Print Parameters
VP94 Load Import Code No. for Japan
VPE1 Create sales representative
VPE2 Change sales representative
VPE3 Display sales representative
VPM4 Merge: Japan - Import Code Number
VPRICAT Maintain and Create Price Catalog
VRRE Returns Delivery for RMA Order
VS01 Create Scale
VS02 Change Scale
VS03 Display Scale
VS04 Create Scale with Reference
VS06 List Scales for Shipment Costs
VT01 Old: Create Shipment
VT01N Create Shipment
VT02 Old: Change Shipment
VT02N Change Shipment
VT03 Old: Display Shipment
VT03N Display Shipment
VT04 Transportation Worklist
VT05 Worklist Shipping: Logs
VT06 Select Shipments: Materials Planning
VT07 Collective run in background
VT11 Select Shipments: Materials Planning
VT12 Select Shipments: Transpt Processing
VT14 Select Shipments: Utilization
VT15 Select Shipments: Free Capacity
VT16 Select Shipments: Check In
VT19 Shipment Tendering Status Monitor
VT20 Overall Shipment Process Monitor
VT22 Display Change-Document Shipment
VT32 Shipment Status list
VT60 Transfer Location Master Data to TPS
VT61 Ext. transport. planning deliveries
VT62 Send Deliveries to Forwarding Agent
VT63 Freight Plng Status from Deliveries
VT68 Deallocate delivery from TPS
VT69 Plan Deliveries from Freight Plng
VT70 Output for Shipments
VTCM List of Continuous Moves
VTRC XSI Cockpit
VTRK Tracking
VV11 Create Output: Sales
VV12 Change output: Sales
VV13 Display Output: Sales
VV21 Create Output: Shipping
VV22 Change output: Shipping
VV23 Display Output: Shipping
VV31 Create Output : Billing
VV32 Change output: Billing
VV33 Display Output: Billing
VV51 Create Output for Sales Activity
VV52 Change Output: Sales Activity
VV53 Display Output: Sales Activity
VV61 Create Output: Handling Units
VV62 Change Output: Handling Unit
VV63 Display Output: Handling Unit
VV71 Create Output: Transportation
VV72 Change Output: Transportation
VV73 Display Output: Transportation
VVG1 Create Output: Group
VVG2 Change output: Groups
VVG3 Display Output: Group
VW01 SD Scenario 'Incoming Orders'
VW02 SD Scenario 'Freedom to Shop'
VX01 Create license (old)
VX01N Create license
VX02 Change license (old)
VX02N Change license
VX03 Display license (old)
VX03N Display license
VX05 Customers for License
VX06 Export Control Classes for License
VX07 Simulation: License Check
VX08 Simulation: Boycott List Check
VX09 Simulation: Embargo Check
VX10 Countries of Destination for License
VX11 Create Financial Document
VX11N Create financial document
VX12N Change Financial Document
VX13N Display financial document
VX14N Maintain financial documents
VX16 BAFA diskette: Selection
VX17 Create BAFA diskette
VX22 Change license data (old)
VX22N Change License Data
VX23 Display license data (old)
VX23N Display license data
VX30 Legal Control: Export Ctrl Class
VX99 FT/Customs: General overview
VXA1 Docs Assigned to Financial Documents
VXA2 Existing Financial Documents
VXA3 Financial Documents: Blocked Docs
VXA5 Document. Payments: Print Monitoring
VXA7 Documentary Payments: Simulation
VXCZ INTRASTAT: Form - Czech Republic
VXHU INTRASTAT: Form - Czech Republic
VXJ1 MITI Declarations
VXJ2 Declaration of ImportBill.Docs Japan
VXPL INTRASTAT: Form - Poland
VXSIM Simulate Import
VXSK INTRASTAT: Form - Slovakia
VY01 Maintain account function modules
VY21 List RFC errors
VY22 Maintain account function modules
VY23 Maintain account function modules
V_I7 Condit: Pricing SD - Index in Backgr
V_NL Edit net price list
V_R2 Display List of Backorders
V_RA Backorder Processing: Selection List
V_SA Collective Proc. Analysis (Deliv.)
V_UC Incomplete SD Documents
V_UC_7 Incomplete SD Documents
V_V2 Updating Sales Documents by Material

SAP - Third Party Sales

Sales Processing using Third Party (w. Shipping Notification)

Scenario Highlights The order is passed to a third party vendor who ships the goods to the customer and bills you. Process Flow In third-party order processing, your company does not deliver the items requested by a customer. Instead, you pass the order along to a third-party vendor who then ships the goods directly to the customer and bills you. The standard sales order automatically creates a purchase requisition for the materials to be delivered by the third-party vendor. In this scenario, the vendor sends a shipping notification. After that a statistical goods receipt is posted. The incoming invoice from the vendor updates the billing quantity, so that the customer-billing document can only be created after entering the invoice from the vendor. Process Flow This scenario consists of the following steps:        A Third-Party Sales Order is created and a purchase requisition is generated automatically        A list of purchase requisitions to be assigned is displayed        The assigned purchase requisitions are converted into purchase orders        The purchase orders are approved        A statistical goods receipt is posted        The vendor invoice is verified and posted        The billing is created Key Points        Reduce stock and costs, increase efficiency        Handover of customer requirements directly to external supplier        Invoice from trader to customer based on quantities from supplier invoice        Fulfillment of customer requirements despite material shortage

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

THIRD PARTY SALES PROCESS
 
GO TO VA01, ENTER THE ORDER TYPE AND SALES AREA
 
ENTER THE CUSTMER, PO NUMBER, ARTICLE(ITEM Category as BANC) AND QTY AND CLICK ON SAVE
 
SERVICE ORDER IS CREATED.
 
GO TO VA02, SELECT THE LINE ITEM CLICK ON GOTO - ITEM-SCHEDULE LINES AND TAKE THE PURCHASE REQUISITION NUMBER
 
GO TO ME21N, ENTER THE PURCHASE REQUISITION NUMBER PRESS ENTER
 
CLICK ON CHECK AND THEN CLICK ON SAVE TO CREATE PO.
 
PO IS CREATED
 
GO TO MIGO FOR POSTING THE STOCK AGAINST PO , ENTER THE PO NUMBER AND PRESS ENTER
 
ENTER THE QTY IN QTY TAB, ENTER STORAGE LOC IN WHERE TAB, SELECT THE ITEM OK, AND THEN CLICK ON CHECK AND SAVE THE DOCUMENT          
GR IS DONE
 
GO TO MIRO FOR POSTING VENDOR INVOICE ENTER THE INVOICE DATE, AMOUNT AND THE PO NUMBER
 
 
ENTER THE BASELINE DATE THEN CLICK ON SIMULATE
 
 
CLICK ON POST
 
 
VENDOR INVOICE IR HAS BEEN DONE
 
Then u can do Delivery and Billing

 

SAP - Inter Company Sales

Inter Company Sales

Scenario Highlights

A customer places an order for goods which you can't fill but can be sourced & shipped from another plant belonging to a company in your group. You invoice the customer & inter-company billing is used.

Process Flow

This scenario shows how sales are processed across company codes.

A customer orders goods from the vendor's sales organization. The vendor has a production / warehouse plant that belongs to a different company code. The goods are produced / contained there and delivered from the production/warehouse plant directly to the customer.

Focus:

Delivering plant belongs to a different company code

Direct delivery from delivering plant to customer

Customer invoice and intercompany billing document

Internal transfer prices

This scenario consists of the following steps:

A sales order is entered

A delivery is created

The goods issue is posted

The billing is created

Intercompany document is created

Key Points

Sales organization and supplying plant can be in different company codes

Inter company sales
Configuration:
1. Create Export Customer 1234 /Account Group/Partner determination
2. Extend the customer
3. Material should exists in both the company codes -- Plants
4. IMG --> SD --> Billing --> InterCompany Billing
a. Define order types for intercompany billing
b. Assign Organizational Units by Plant
c. Define Internal customer by Sales Organization
d. Automatic posting to Vendor Account (for us it is plant 1001)
e. Assignment of sales organization - Dist. Channel - Plant
f. Maintain Condition records for PI01 in Vk11with ordering sales org and supplying plant
g. Create two billing documents
1. IV raised by delivering plant to Ordering plant
2. F2 Invoice to be raised to customer

4. Purchase order has to be created for intercompany billing
5. Item Category creation, (CS)Schedule line category creation
6. Use Pricing Procedure ICaa01 for Supplying sales organization
Transactions:
1. Create a Order(ZINT) for Export Customer1234 to Company Code 2001
2. Run an Avaialbility Check material stock not available.
3. Creates purchase requisition.
4. Company code 2001 raises a PO to Company Code 1001
5. Company code picks/packs and delivers the goods to End customer(Based on customer details)
6. Company 1001 raises an intercompany invoice
7. Upon receiving the intercompany invoice the company code 2001 raises a normal invoice to the customer

OR u can also refer these steps

Follow the steps for Inter company scenario:

1. Define doc type IV and assign it to your sales order type.
2. Assign its( customers) own sales area to the supplying plant.
3. Create a customer under supplying sales area and assign it to the ordering
sales area.
4. Assign the supplying plant to the ordering sales area.
5. Material should be present in both plants.
6. Assign procedure ICA001 for the supplying sales organisation with Dopp as I
and Cupp in CMD as 1.
7. Maintain the condition record for PI01 with ordering Sales org and Supplying
Plant.
8. Run a sales order and manually enter the supplying plant then do Del, Picking
and PGI.
9. Go to billing first system generates normal invoice and later repeat the same
process in billing to generate intercompany billing.

SAP Repair/Service Process

REPAIR OR SERVICE PROCESS

GOTO MM41 CREATE A NON VALUATED ARTICLE WITH ITEM CATEGORY DIEN (SERVICE)

GOTO VA01 FOR CREATE SERVICE ORDER, ENTER ORDER TYPE OR AND ENTER SALES AREA

ENTER CUSTOMER, PO NUMBER, MATERIAL, QUANTITY THEN SAVE THE ORDER

SERVICE ORDER will BE CREATED

GO TO MIGO FOR MAKING GR BASED ON THE SALES ORDER WITH MOVEMENT TYPE 501 E , ENTER ARTICLE , QTY, SALES ORDER, SITE

CLICK ON CHECK AND THEN SAVE

GR HAS BEEN DONE, ARTICLE TAKEN INSIDE THE STOCK

GOTO VLO1N FOR DELIVERY

CLICK ON PGI

GO TO VF01 FOR CREATING BILLING

PRESS ENTER AND SAVE THE DOCUMENT.

SERVICE BILL IS CREATED

SAP Introduction

An Introduction to SAP

SAP was founded in 1972 in Walldorf, Germany. It stands for Systems, Applications and Products in Data Processing. Over the years, it has grown and evolved to become the world premier provider of client/server business solutions for which it is so well known today. The SAP R/3 enterprise application suite for open client/server systems has established a new standards for providing business information management solutions.

SAP product are consider excellent but not perfect.  The main problems with software product is that it can never be perfect.

The main advantage of using SAP as your company ERP system is that SAP have a very high level of integration among its individual applications which guarantee consistency of data throughout the system and the company itself.

In a standard SAP project system, it is divided into three environments, Development, Quality Assurance and Production.

The development system is where most of the implementation work takes place. The quality assurance system is where all the final testing is conducted before moving the transports to the production environment.  The production system is where all the daily business activities occur.  It is also the client that all the end users use to perform their daily job functions.

To all company, the production system should only contains transport that have passed all the tests.

SAP is a table drive customization software.  It allows businesses to make rapid changes in their business requirements with a common set of programs.  User-exits are provided for business to add in additional source code.  Tools such as screen variants are provided to let you set fields attributes whether to hide, display and make them mandatory fields.

This is what makes ERP system and SAP in particular so flexible.  The table driven customization are driving the program functionality instead of those old fashioned hard-coded programs.  Therefore, new and changed business requirements can be quickly implemented and tested in the system.

Many other business application software have seen this table driven customization advantage and are now changing their application software based on this table customizing concept.

In order to minimized your upgrading costs, the standard programs and tables should not be changed as far as possible.  The main purpose of using a standard business application software like SAP is to reduced the amount of time and money spend on developing and testing all the programs.  Therefore, most companies will try to utilized the available tools provided by SAP.

What is Client? What is the difference between Customization and Configuration?

The difference between cutomizing and configuration is:
- CONFIGURATION: we will configure the system to meet the needs of your business by using the existing data.
- CUSTOMIZING: we will customise or adapt the system to your business requirements, which is the process of mapping SAP to your business process.
- CLIENT: A client is a unique one in organizational structure, can have one or more company codes. Each company code is its own legal entity in finance.

Configuration  vs. Customization
When considering enterprise software of any type, it is important to understand the difference between configuration and customization.The crux of the difference is complexity. Configuration uses the inherent flexibility of the enterprise software to add fields, change field names,modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets. Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version.Wherever possible, governments should avoid customization by using configuration to meet their goals.Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors.        *-- Sivaprasad, Sonali Sardesai

What is SAP R3?
We know that SAP R/3 is software, it particular it is client-server software. This means that the groups/layers 
that make up a R/3 System are designed to run simultaneously across several separate computer systems. 

When you install Microsoft Excel on your PC, each component of Excel (printing components, graphing components, word processing components, and etc.) is stored, managed, and processed via the hardware of your PC.   When a company installs SAP's software each component (or "layer" in R/3's case) is stored, managed, and processed via the hardware of separate and specialized computer systems. Each of the various layers is capable of calling upon the specialty of any of the other installed layers in order to complete a given task. 

Those components/layers that are requesting services are called "clients", those components/layers that are providing services are called "servers".  Thus the term - "client/server".        *-- Shailesh Kumar (shailesh_das@yahoo.com)

What is meant by SAP ECC?

SAP is an ERP (Enterprise Resource Planning) module, ECC is the version of SAP, like 4.6, 4.6c and 4.7 in that series new version is ECC-6. Its known as Enterprise core component.

SAP TABLES

 

 

	Tables in SAP Just a list of tables that come in handy. Sales orders Name Description Uses LIKP Shipped Lines header   LIPS Shipped Lines detail   VBAK Order header Every order (unless archiving) VBAP Table fields Every line item (unless archiving) VBBE Open sales order line items Great file, but be careful. Contents don't reflect orders that do not affect purchasing (go figure). VBEP Schedule line item   VBFA Document flow Let's you move from order to shipping document to invoice. VBUK Order status   VBUP Line item detail status   VBFK Invoicing header   VBFP Invoicing detail   Material Management Name Description Uses MARA Inventory Master MARC Plant Data MARD Current Inventory MAKT Descriptions MBEW Material Valuation T179 Product Hierarchy MVKE Sales data (materials) MKPF Material document Status code 'R' in VBFA Purchasing Name Description Uses EINA Purchasing inforecord by MATNR/LIFNR contains things like vendor material number and access key for EINE EINE Purchasing inforecord detail Contains minimum purchase, group, currency EKPO Purchase orders   EKET Scheduled lines   EKES Vendor confirmed lines         Forecasting Name Description Uses MAPR PROP PROW Classification Name Description Uses KSSK Material number to class KLAS Class description KSML Characteristic name CABN/CABNT Characteristic name description CAWN/CAWNT Characteristic name AUSP Numeric values Name Description Uses CAUFV Service order header AFPO Service order line Holds items that will create "reservations" RESB SM Reservations Materials needed for line Customer Data KNA1 Customer Master   KNVV Sales information   KNVP Partners (ship-to, etc)                       System tables Name Description Uses DD02T Table texts DD03L Table fields Lists the fields in a table DD04T Data element texts USR02 Valid user names Config tables (normally begin with "T") Name Description Uses T001 Client table T002 Languages T005 Region (Country) TCURR Currency and exchange rates TVAK Order type TVSB Shipping condition TVAGT Rejected reason for order line Other tables Name Description Uses STXH Text header STXL Text detail

SAP SD Process

J54 Third Party Processing With Shipping Notification

Transaction code transaction text
VA01 Create Sales Order
ME21N Purchase Order Processing
MIGO Goods Receipt Based on Shipping Notification
VF01 Billing Processing
MIRO Invoice Verification

J55 Third Party Processing Without Shipping Notification

Transaction code transaction text
VA01 Create Sales Order
ME21N Purchase Order Processing
MIRO Invoice Verification
VF01 Billing Processing

J56 Bought-In Item

Transaction code transaction text
VA01 Sales Order
ME21N Purchase Order
MIGO_GR Goods Receipt
VL01N Delivery Processing
VF01 Billing Processing
MIRO Invoice Verification

J57 Extended Sales Order Processing

Transaction code transaction text
VA01 Creating Sales Order
VL01N Creating Delivery
VF01 Creating Billing

J58 Consignment Processing

Transaction code transaction text
VA01 Order
VL01N Delivery
VL02N Picking
VL02N Goods Issue
MMBE Stock Overview After Consignment Fill-Up
VA01 Order
VL01N Delivery
VL02N Picking
VL02N Goods Issue
VF01 Billing
VA01 Order
VL01N Delivery
VL02N Goods Receipt

J59 Returns and Complaints

Transaction code transaction text
VA01 Creating Sales Order
VL01N Creating a Delivery
VF01 Creating Billing
QM01 Creating Quality Notification for Customer Complaints
VA01 Creating Credit Memo (Value)
V23 Releasing Credit Memo to Billing
VF01 Billing
VA01 Creating Returns
VA03 Displaying Batch for Return
VL01N Creating Returns Delivery
QA32 Inspecting Goods Receipt
QA32 Creating Usage Decision
MB1B Booking Returns to Relevant Stock
QE51N Quality Inspections and Booking Returns into Unrestricted or Blocked Stock
V23 Releasing Returns to Billing
VF01 Billing

J60 Returnables Processing

Transaction code transaction text
VA01 Creating Sales Order
MMBE Displaying Pallets Stock
VL01N Creating Delivery and Picking
VF01 Creating Billing
MMBE Displaying Pallets Stock
VA01 Creating Sales Order for the Return
VL01N Creating Delivery
VL01NO Creating Delivery Pallets Return without Order Reference
MMBE Displaying Pallets Stock
VA01 Creating Debit Memo Request for Unreturned Pallets
V.23 Releasing Debit Memo Request to Billing
VF01 Creating Billing
MB1A Posting Unreturned Pallets
MMBE Displaying Pallets Stock

J61 Batch Recall
Transaction code transaction text
VA01 Sales Order Processing and Delivery (optional)
VC01N_M Sales Activity – Direct Mailing
SA38 Generate Follow-up Sales Activities
VC01N Processing Follow-up Sales Activities
VC01N Returns
VL01N Shipping: Returns Delivery
QA32 Quality Inspections for Deliveries: Inspecting Goods Receipt
QA32 Creating Usage Decision
MB1B Booking Returns to Unrestricted or Blocked Stock
V.23 Release Credit Memo to Billing
VF01 Create Billing

J62 Cross-Company-Code Sales Processing

Transaction code transaction text
VA01 Sales Order Processing (in Sales Org. BP01)
VL01N Process: Create Delivery
VF04 Create Customer Invoice in the Sales Organization
VF03 Display Customer Invoice Details
VF04 Create an Invoice (internally) in the Plant executing
the Delivery
VF03 Displaying Details on the Intercompany Billing Document (IV)
FB03 Display Details on the Inter-company Billing Document
FF67 Entering and Posting a Manual Account Statement
FEBA Postprocessing an Account Statement

J63 Sales Order Processing with 1st Time Customer
Transaction code transaction text
VA01 Creating Sales Order
VA02 Changing Sales Order

J89 Sales of Services
Sales Order creation
Invoice creation

J91 Export sales under bond
Creating Inquiry
Creating Quotation
Creating Sales Order
Creating Pro Forma Invoice
Creating Outbound delivery
Creating Billing document
Printing Billing document
Creating Excise Invoice
Printing Excise Invoice
Creating Excise Bond
Creating ARE- 1
Printing ARE- 1
Posting ARE- 1
Updating ARE- 1
Updating ARE- 1 - Countersigned by customs
Updating ARE- 1- Document Approved & returns by customs
Updating ARE- 1- Sending ARE-1 to Excise department
Updating ARE- 1- Closing ARE-1 once Excise clears the document

J95 Sales at Depot
Customer and Material masters
Creating Sales order
Creating Delivery document
Creating Depot Excise Invoice
Creating Billing document

J96 Deemed Export
Creating Inquiry
Creating Quotation
Capture License
Creating Sales Order
Creating Pro Forma Invoice
Creating Outbound delivery
Creating Billing document
Printing Billing document
Creating Excise Invoice
Printing Excise Invoice
Creating ARE- 3
Printing ARE- 3
Posting ARE- 3
Updating ARE- 3
Closing ARE- 3

Reporting

Standard Reports - Refer: 'Sales - Std Reports' tab

Data Migration
ID ~ Sales & Distribution Description
DC_SD001 Pricing Conditions
DC_SD002 Sales order



Forms
ID ~ Sales Description
FO_SA001 Customer inquiry
FO_SA002 Quotation
FO_SA003 Order confirmation
FO_SA004 Contract
FO_SA005 Invoice
FO_SA006 Scheduling agreement
FO_SA007 Cash Sales
ID ~ Delivery Description
additional information
FO_DL001 Picking List
FO_DL002 Delivery Note

SAP Automatic Posting OBYC_GBB

Configure Automatic Postings
In this step, you enter the system settings for Inventory Management
and Invoice Verification transactions for automatic postings to G/L
accounts.
You can then check your settings using a simulation function.
Under Further information there is a list of transactions in Materials
Management and their definitions.
What are automatic postings?
Postings are made to G/L accounts automatically in the case of Invoice
Verification and Inventory Management transactions relevant to
Financial and Cost Accounting.
Example:
Posting lines are created in the following accounts in the case of a
goods issue for a cost center:
• Stock account
• Consumption account
How does the system find the relevant accounts?
When entering the goods movement, the user does not have to enter a
G/L account, since the ERP system automatically finds the accounts to
which postings are to be made using the following data:
• Chart of accounts of the company code
If the user enters a company code or a plant when entering a
transaction, the ERP system determines the chart of accounts which is
valid for the company code.
You must define the automatic account determination individually for
each chart of accounts.
• Valuation grouping code of the valuation area
If the automatic account determination within a chart of accounts is
to run differently for certain company codes or plants (valuation
areas), assign different valuation grouping codes to these valuation
areas.
You must define the automatic account determination individually for
every valuation grouping code within a chart of accounts. It applies
to all valuation areas which are assigned to this valuation grouping
code.
If the user enters a company code or a plant when entering a
transaction, the system determines the valuation area and the
valuation grouping code.
• Transaction/event key (internal processing key)
Posting transactions are predefined for those inventory management and
invoice verification transactions relevant to accounting. Posting
records, which are generalized in the value string, are assigned to
each relevant movement type in inventory management and each
transaction in invoice verification. These contain keys for the
relevant posting transaction (for example, inventory posting and
consumption posting) instead of actual G/L account numbers.
You do not have to define these transaction keys, they are determined
automatically from the transaction (invoice verification) or the
movement type (inventory management). All you have to do is assign the
relevant G/L account to each posting transaction.
• Account grouping (only for offsetting entries, consignment
liabilities, and price differences)
Since the posting transaction "Offsetting entry for inventory posting"
is used for different transactions (for example, goods issue,
scrapping, physical inventory), which are assigned to different
accounts (for example, consumption account, scrapping, expense/income
from inventory differences), it is necessary to divide the posting
transaction according to a further key: account grouping code.
An account grouping is assigned to each movement type in inventory
management which uses the posting transaction "Offsetting entry for
inventory posting".
Under the posting transaction "Offsetting entry for inventory
posting", you must assign G/L accounts for every account grouping,
that is, assign G/L accounts.
If you wish to post price differences to different price difference
accounts in the case of goods receipts for purchase orders, goods
receipts for orders, or other movements, you can define different
account grouping codes for the transaction key.
Using the account grouping, you can also have different accounts for
consignment liabilities and pipeline liabilities.
• Valuation class of material or (in case of split valuation) the valuation type
The valuation class allows you to define automatic account
determination that is dependent on the material. for example: you post
a goods receipt of a raw material to a different stock account than if
the goods receipt were for trading goods, even though the user enters
the same transaction for both materials.
You can achieve this by assigning different valuation classes to the
materials and by assigning different G/L accounts to the posting
transaction for every valuation class.
If you do not want to differentiate according to valuation classes you
do not have to maintain a valuation class for a transaction.
Requirements
Before you maintain automatic postings, you must obtain the following
information:
1. Valuation level ( plant or company code)
Establish whether the materials are valuated at plant or at company code level
When valuation is at plant level, the valuation area corresponds to a plant.
When valuation is at company code level, the valuation area
corresponds to a company code.
Define valuation level
2. Chart of accounts and valuation grouping code per valuation area
Find out whether the valuation grouping code is active.
Activate split valuation
If it is not active, determine the chart of accounts assigned to each
valuation area (via the company code).
If it is active, determine the chart of accounts and the valuation
grouping code assigned to each valuation area.
Group valuation areas
You must define a separate account determination process for chart of
accounts and each valuation grouping code.
3. Valuation class per material type
If you wish to differentiate the account determination process for
specific transactions according to valuation classes, find out which
valuation classes are possible for each material type.
Define valuation classes
4. Account grouping for offsetting entries to stock accounts
Under Define account grouping for movement types, determine for which
movement types an account grouping is defined for the
transaction/event keys GGB (offsetting entry to stock posting), KON
(consignment liabilities) and PRD (price differences).
Default settings
G/L account assignments for the charts of accounts INT and the
valuation grouping code 0001 are SAP standard.
Activities
1. Create account keys for each chart of accounts and each valuation
grouping code for the individual posting transactions. To do so,
proceed as follows:
a) Call up the activity Configure Automatic Postings.
The ERP system first checks whether the valuation areas are correctly
maintained. If, for example, a plant is not assigned to a company
code, a dialog box and an error message appear.
From this box, choose Continue (next entry) to continue the check.
Choose Cancel to end the check.
The configuration menu Automatic postings appears.
b) Choose Goto -> Account assignment.
A list of posting transactions in Materials Management appears. For
further details of the individual transactions, see Further
information.
The Account determination indicator shows whether automatic account
determination is defined for a transaction.
c) Choose a posting transaction.
A box appears for the first posting transaction. Here you can enter a
chart of accounts.
You can enter the following data for each transaction:
o Rules for account number assignments
With Goto -> Rules you can enter the factors on which the account
number assignments depend:
- debit/credit indicator
- general grouping (= account grouping)
- valuation grouping
- valuation class
o Posting keys for the posting lines
Normally you do not have to change the posting keys. If you wish to
use new posting keys, you have to define them in the Customizing
system of Financial Accounting.
o Account number assignments
You must assign G/L accounts for each transaction/event key (except
KBS). You can assign these accounts manually or copy them from another
chart of accounts via Edit -> Copy.
If you want to differentiate posting transactions (e.g. inventory
postings) according to valuation classes, you must make an account
assignment for each valuation class.
Using the posting transaction "Offsetting entry for inventory
posting", you have to make an account assignment for each account
grouping
If the transaction PRD (price differences) is also dependent on the
account grouping, you must create three account assignments:
- an account assignment without account grouping
- an account assignment with account grouping PRF
- an account assignment with account grouping PRA
If the transaction KON (consignment and pipeline liabilities) is also
dependent on the account grouping, you must create two account
assignments:
- an account assignment without account grouping (consignment)
- an account assignment with account grouping (pipeline)
d) Save your settings.
2. Then check your settings with the simulation function.
With the simulation function, you can simulate the following:
o Inventory Management transactions
o Invoice Verification transactions
When you enter a material or valuation class, the ERP system
determines the G/L accounts which are assigned to the corresponding
posting transactions. Depending on the configuration, the SAP system
checks whether the G/L account exists
In the simulation you can compare the field selection of the movement
type with that of the individual accounts and make any corrections.
If you want to print the simulation, choose Simulation -> Report.
To carry out the simulation, proceed as follows:
a) Choose Settings to check the simulation defaults for
- the application area (Invoice Verification or Inventory Management)
- the input mode (material or valuation class)
- account assignment
Instructions
b) Choose Goto -> Simulation.
The screen for entering simulation data appears.
c) Depending on the valuation level, enter a plant or a company code
on the screen.
d) When you simulate Inventory Management transactions, goods
movements are simulated. The ERP system suggests the first movement
type for simulation. If several movements are possible with this
movement type, you can select a line.
When you simulate Invoice Verification transactions, a list appears on
the screen of the possible transaction types. Select a line.
e) Then choose Goto -> Account assignments.
A list appears of the posting lines which can be created by the
selected transaction. For each posting line, the G/L account for the
debit posting as well as the G/L account for the credit posting are
displayed.
f) From this screen, choose Goto -> Movement+ to get a list of the
posting lines for the next movement type or transaction type.
If you work with valuation classes, choose Goto -> Valuation class+ to
receive the simulation for the next valuation class. This function is
not possible when simulating with material numbers.
Choose Goto -> Check screen layout to compare the movement type with
the G/L accounts determined by the system and make any necessary
corrections.
Note
The simulation function does NOT obviate the need for a trial posting!
Further notes
The following list shows the individual transactions with examples of
how they are used. The transaction/event key is specified in brackets.
• Agency business: income (AG1)
This transaction can be used in agency business for income deriving
from commission (e.g. del credere commission). The account key is used
in the calculation schemas for agency business to determine the
associated revenue accounts.
• Agency business: turnover (AG2)
This transaction can be used in agency business if turnover (business
volume) postings are activated in Customizing for the payment types.
The account key is specified in Customizing for the billing type.
• Agency business: expense (AG3)
This transaction can be used in agency business for commission
expenses. The account key is used in the calculation schemas for
agency business to determine the associated expense accounts.
• Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of
withdrawals from consignment stock or when consignment stock is
transferred to own stock if the material is subject to standard price
control and the consignment price differs from the standard price.
• Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to
another if the complete value of the issuing material cannot be posted
to the value of the receiving material. This applies both to materials
with standard price control and to materials with moving average price
control. Price differences can arise for materials with moving average
price if stock levels are negative and the stock value becomes
unrealistic as a result of the posting. Transaction AUM can be used
irrespective of whether the transfer posting involves a transfer
between plants. The expenditure/income is added to the receiving
material.
• Provisions for subsequent (end-of-period rebate) settlement (BO1)
If you use the "subsequent settlement" function with regard to
conditions (e.g. for period-end volume-based rebates), provisions for
accrued income are set up when goods receipts are recorded against
purchase orders if this is defined for the condition type.
• Income from subsequent settlement (BO2)
The rebate income generated in the course of "subsequent settlement"
(end-of-period rebate settlement) is posted via this transaction.
• Income from subsequent settlement after actual settlement (BO3)
If a goods receipt occurs after settlement accounting has been
effected for a rebate arrangement, no further provisions for accrued
rebate income can be managed by the "subsequent settlement" facility.
No postings should be made to the account normally used for such
provisions. As an alternative, you can use this transaction to post
provisions for accrued rebate income to a separate account in cases
such as the one described.
• Supplementary entry for stock (BSD)
This account is posted when closing entries are made for a cumulation
run. This account is a supplementary account to the stock account;
that is, the stock account is added to it to determine the stock value
that was calculated via the cumulation. In the process, the various
valuation areas (for example, commercial, tax), that are used in the
balance sheet are taxed separately.
• Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time goods
receipts are recorded or subsequent adjustments made with regard to
subcontract orders.
If the account assigned here is defined as a cost element, you must
specify a preliminary account assignment for the account in the table
of automatic account assignment specification (Customizing for
Controlling) in order to be able to post goods receipts against
subcontract orders. In the standard system, cost center SC-1 is
defined for this purpose.
• Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such
postings are effected, for example:
o In inventory management in the case of goods receipts to own stock
and goods issues from own stock
o In invoice verification, if price differences occur in connection
with incoming invoices for materials valuated at moving average price
and there is adequate stock coverage
o In order settlement, if the order is assigned to a material with
moving average price and the actual costs at the time of settlement
vary from the actual costs at the time of goods receipt
Because this transaction is dependent on the valuation class, it is
possible to manage materials with different valuation classes in
separate stock accounts.
Caution
Take care to ensure that:
o A stock account is not used for any transaction other than BSX
o Postings are not made to the account manually
o The account is not changed in the productive system before all stock
has been booked out of it
Otherwise differences would arise between the total stock value of the
material master records and the balance on the stock account.
Account determination of valuated sales order stock and project stock
Note that for valuated sales order stock and project stock (special
stock E and Q) and for the transaction/event keys BSX and GBB, you
must maintain an account determination to avoid receiving warning
messages when entering data (purchase order or transfer posting) for
valuated stock.
During data entry, the system attempts to execute a provisional
account determination for GBB for valuated stock. The system will only
replace the provisional account determination for GBB with the correct
account determination for the stock account (BSX), in the background,
if you enter the data for valuated stock at a later point in time.
• Revaluation of other consumption (COC)
This transaction/event key is required for the revaluation of
consumption in Actual Costing/Material Ledger.
Revaluation of consumption valuates single-level consumption using the
actual prices determined in the Actual Costing/Material Ledger
application. This revaluation can either take place in the account
where the original postings were made, or in a header account.
The header account is determined using the transaction/event key COC.
• Del credere (DEL)
Transaction/event key for the payment/invoice list documents in
Purchasing. The account key is needed in the calculation schema for
payment/settlement processing to determine the associated revenue
accounts.
• Small differences, Materials Management (DIF)
This transaction is used in Invoice Verification if you define a
tolerance for minor differences and the balance of an invoice does not
exceed the tolerance.
• Purchase account(EIN), purchase offsetting account (EKG), freight
purchase account (FRE)
These transactions are used only if Purchase Account Management is
active in the company code.
Note
Due to special legal requirements, this function was developed
specially for certain countries (Belgium, Spain, Portugal, France,
Italy, and Finland).
Before you use this function, check whether you need to use it in your country.
• Freight clearing (FR1), provision for freight charges (FR2), customs
duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental
procurement costs) in the case of goods receipts against purchase
orders and incoming invoices. Which transaction is used for which
delivery costs depends on the condition types defined in the purchase
order.
You can also enter your own transactions for delivery costs in condition types.
• External service (FRL)
The transaction is used for goods and invoice receipts in connection
with subcontract orders.
If the account assigned here is defined as a cost element, you must
specify a preliminary account assignment for the account in the table
of automatic account assignment specification (Customizing for
Controlling) in order to be able to post goods receipts against
subcontract orders. In the standard system, cost center SC-1 is
defined for this purpose.
• External service, delivery costs (FRN)
This transaction is used for delivery costs (incidental costs of
procurement) in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must
specify a preliminary account assignment for the account in the table
of automatic account assignment specification (Customizing for
Controlling) in order to be able to post goods receipts against
subcontract orders. In the standard system, cost center SC-1 is
defined for this purpose.
• Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory
Management. They are dependent on the account grouping to which each
movement type is assigned. The following account groupings are defined
in the standard system:
o AUA: for order settlement
o AUF: for goods receipts for orders (without account assignment)
and for order settlement if AUA is not maintained
o AUI: Subsequent adjustment of actual price from cost center directly
to material (with account assignment)
o BSA: for initial entry of stock balances
o INV: for expenditure/income from inventory differences
o VAX: for goods issues for sales orders without
account assignment object (the account is not a cost element)
o VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
o VBO: for consumption from stock of material provided to vendor
o VBR: for internal goods issues (for example, for cost center)
o VKA: for sales order account assignment
(for example, for individual purchase order)
o VKP: for project account assignment (for example, for individual PO)
o VNG: for scrapping/destruction
o VQP: for sample withdrawals without account assignment
o VQY: for sample withdrawals with account assignment
o ZOB: for goods receipts without purchase orders (mvt type 501)
o ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to post
goods issues for cost centers (mvt type 201) and goods issues for
orders (mvt type 261) to separate consumption accounts, you can assign
the account grouping ZZZ to movement type 201 and account grouping YYY
to movement type 261.
Caution
If you use goods receipts without a purchase order in your system
(movement type 501), you have to check to which accounts the account
groupings are assigned ZOB
If you expect invoices for the goods receipts, and these invoices can
only be posted in Accounting, you can enter a clearing account
(similar to a GR/IR clearing account though without open item
management), which is cleared in Accounting when you post the vendor
invoice.
Note that the goods movement is valuated with the valuation price of
the material if no external amount has been entered.
As no account assignment has been entered in the standard system, the
assigned account is not defined as a cost element. If you assign a
cost element, you have to enter an account assignment via the field
selection or maintain an automatic account assignment for the cost
element.
Account determination of valuated sales order stock and project stock
Note that for valuated sales order stock and project stock (special
stock E and Q) and for the transaction/event keys BSX and GBB, you
must maintain an account determination to avoid receiving warning
messages when entering data (purchase order or transfer posting) for
valuated stock.
During data entry, the system attempts to execute a provisional
account determination for GBB for valuated stock. The system will only
replace the provisional account determination for GBB with the correct
account determination for the stock account (BSX), in the background,
if you enter the data for valuated stock at a later point in time.
• Purchase order with account assignment (KBS)
You cannot assign this transaction/event key to an account. It means
that the account assignment is adopted from the purchase order and is
used for the purpose of determining the posting keys for the goods
receipt.
• Exchange Rate Differences Materials Management(AVR) (KDG)
When you carry out a revaluation of single-level consumption in the
material ledger for an alternative valuation run, the exchange rate
difference accounts of the materials are credited with the exchange
rate differences that are to be assigned to the consumption.
• Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an
invoice relating to a purchase order is posted with a different
exchange rate to that of the goods receipt and the material cannot be
debited or credited due to standard price control or stock
undercoverage/shortage.
• Differences due to exchange rate rounding, Materials Management (KDR)
An exchange rate rounding difference can arise in the case of an
invoice made out in a foreign currency. If a difference arises when
the posting lines are translated into local currency (as a result of
rounding), the system automatically generates a posting line for this
rounding difference.
• Exchange Rate Differences from Lower Levels (KDV)
In multi-level periodic settlement in the material ledger, some of the
exchange rate differences that have been posted during the period in
respect of the raw materials, semifinished products and cost centers
performing the activity used in the manufacture of a semifinished or
finished product are debited or credited to that semifinished or
finished product.
• Consignment liabilities (KON)
Consignment liabilities arise in the case of withdrawals from
consignment stock or from a pipeline or when consignment stock is
transferred to own stock.
Depending on the settings for the posting rules for the
transaction/event key KON, it is possible to work with or without
account modification. If you work with account modification, the
following modifications are available in the standard system:
o None for consignment liabilities
o PIP for pipeline liabilities
• Offsetting entry for price differences in cost object hierarchies (KTR)
The contra entry for price difference postings (transaction PRK)
arising through settlement via material account determination is
carried out with transaction KTR.
• Accruals and deferrals account (material ledger) (LKW)
If the process of material price determination in the material ledger
is not accompanied by revaluation of closing stock, the price and
exchange rate differences that should actually be applied to the stock
value are contra-posted to accounts with the transaction/event key
LKW.
If, on the other hand, price determination in the material ledger is
accompanied by revaluation of the closing stock, the price and
exchange rate differences are posted to the stock account (i.e. the
stock is revalued).
• Price Difference from Exploded WIP (Lar.) (PRA)
If you use the WIP revaluation of the material ledger, the price
variances of the exploded WIP stock of an activity type or a business
process are posted to the price differences account with
transaction/event key PRA.
• Differences (AVR Price) (PRC)
In the alternative valuation run in the material ledger, some of the
variances that accrue interest in the cost centers, are transfer
posted to the semifinished or finished product.
• Price differences (PRD)
Price differences arise for materials valuated at standard price in
the case of all movements and invoices with a value that differs from
the standard price. Examples: goods receipts against purchase orders
(if the PO price differs from the standard pricedardpreis), goods
issues in respect of which an external amount is entered, invoices (if
the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving
average price if there is not enough stock to cover the invoiced
quantity. In the case of goods movements in the negative range, the
moving average price is not changed. Instead, any price differences
arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event
key PRD, it is possible to work with or without account modification.
If you use account modification, the following modifications are
available in the standard system:
o None for goods and invoice receipts against purchase orders
o PRF for goods receipts against production orders and
order settlement
o PRA for goods issues and other movements
o PRU for transfer postings (price differences in the case
of external amounts)
• Price Differences (Material Ledger, AVR) (PRG)
When you carry out a revaluation of single-level consumption in the
material ledger during the alternative valuation run, the price
difference accounts of the materials are credited with the price
differences that are to be assigned to the consumption.
• Price differences in cost object hierarchies (PRK)
In cost object hierarchies, price differences occur both for the
assigned materials with standard price and for the accounts of the
cost object hierarchy. In the course of settlement for cost object
hierarchies after settlement via material account determination, the
price differences are posted via the transaction PRK.
• Price Difference from Exploded WIP (Mat.) (PRM)
If you use the WIP revaluation of the material ledger, the price and
exchange rate differences of the exploded WIP stock of a material are
posted to the price difference account with transaction/event key PRM.
• Price differences, product cost collector (PRP)
During settlement accounting with regard to a product cost collector
in repetitive manufacturing, price differences are posted with the
transaction PRP in the case of the valuated sales order stock.
This transaction is currently used in the following instances only:
- Production cost collector in Release 4.0
- Product cost collector in IS Automotive Release 2.0 (product cost
collector in connection with APO)
• Offsetting entry: price differences, product cost collector (PRQ)
The offsetting (contra) entry to price difference postings
(transaction PRP) in the course of settlement accounting with respect
to a product cost collector in repetitive manufacturing in the case of
the valuated sales order stock is carried out via transaction PRQ.
This transaction is currently used in the following instances only:
- Production cost collector in Release 4.0
- Product cost collector in IS Automotive Release 2.0 (product cost
collector in connection with APO)
• Price Differences from Lower Levels (PRV)
In multi-level periodic settlement in the material ledger, some of the
price differences posted during the period in respect of the raw
materials, semifinished products, and cost centers performing the
activity used in a semifinished or finished product, are transfer
posted to that semifinished or finished product.
• Price differences for material ledger (PRY)
In the course of settlement in the material ledger, price differences
from the material ledger are posted with the transaction PRY.
• Expense and revenue from revaluation (retroactive pricing, RAP)
This transaction/event key is used in Invoice Verification within the
framework of the revaluation of goods and services supplied for which
settlement has already taken place. Any difference amounts determined
are posted to the accounts assigned to the transaction/event key RAP
(retroactive pricing) as expense or revenue.
At the time of the revaluation, the amounts determined or portions
thereof) are posted neither to material stock accounts nor to price
difference accounts. The full amount is always posted to the "Expense
from Revaluation" or "Revenue from Revaluation" account. The
offsetting (contra) entry is made to the relevant vendor account.
• Invoice reductions in Logistics Invoice Verification (RKA)
This transaction/event key is used in Logistics Invoice Verification
for the interim posting of price differences in the case of invoice
reductions.
If a vendor invoice is reduced, two accounting documents are
automatically created for the invoice document. With the first
accounting document, the amount invoiced is posted in the vendor line.
An additional line is generated on the invoice reduction account to
partially offset this amount. With the second accounting document, the
invoice reduction is posted in the form of a credit memo from the
vendor. The offsetting entry to the vendor line is the invoice
reduction account. Hence the invoice reduction account is always
balanced off by two accounting documents within one transaction.
• Provision for delivery costs (RUE)
Provisions are created for accrued delivery costs if a condition type
for provisions is entered in the purchase order. They must be cleared
manually at the time of invoice verification.
• Taxes in case of transfer posting GI/GR (TXO)
This transaction/event key is only relevant to Brazil (nota fiscal).
• Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and in
Invoice Verification if the standard price of a material has been
changed and a movement or an invoice is posted to the previous period
(at the previous price).
• Expenditure/income from revaluation (UMD)
This account is the offsetting account for the BSD account. It is
posted during the closing entries for the cumulation run of the
material ledger and has to be defined for the same valuation areas.
• Unplanned delivery costs (UPF)
Unplanned delivery costs are delivery costs (incidental procurement
costs) that were not planned in a purchase order (e.g. freight,
customs duty). In the SAP posting transaction in Logistics Invoice
Verification, instead of distributing these unplanned delivery costs
among all invoice items as hitherto, you have the option of posting
them to a special account. A separate tax code can be used for this
account.
• Input tax, Purchasing (VST)
Transaction/event key for tax account determination within the
"subsequent settlement" facility for debit-side settlement types. The
key is needed in the settlement schema for tax conditions.
• Inflation posting (WGB)
Transaction/event key that posts inflation postings to a different
account, within the handling of inflation process for the period-end
closing.
• Goods issue, revaluation (inflation) (WGI)
This transaction/event key is used if already-posted goods issues have
to be revaluated following the determination of a new market price
within the framework of inflation handling.
• Goods receipt, revaluation (inflation) (WGR)
This transaction/event key is used if already-effected transfer
postings have to be revaluated following the determination of a new
market price within the framework of inflation handling. This
transaction is used for the receiving plant, whereas transaction WGI
(goods receipt, revaluation (inflation)) is used for the plant at
which the goods are issued.
• WIP from Price Differences (Internal Activity) (WPA)
When you use the WIP revaluation of the material ledger, the price
variances from the actual price calculation that are to be assigned to
the WIP stock, an activity type or a business process are posted to
the WIP account for activities.
• WIP from Price Differences (Material) (WPM)
When you use the WIP revaluation of the material ledger, the price and
exchange rate differences that are to be assigned to the WIP stock of
a material are posted to the WIP account for material.
• GR/IR clearing (WRX)
Postings to the GR/IR clearing account occur in the case of goods and
invoice receipts against purchase orders. For more on the GR/IR
clearing account, refer to the SAP Library (documentation MM Material
Valuation).
Caution
You must set the Balances in local currency only indicator for the
GR/IR clearing account to enable the open items to be cleared. For
more on this topic, see the field documentation.
• GR/IR clearing for material ledger (WRY)
This transaction/event key is not used from Release 4.0 onwards.
Prior to 4.0, it was used for postings to the GR/IR clearing account
if the material ledger was active. As of Release 4.0, the transaction
is no longer necessary, since postings to the GR/IR account in
parallel currencies are possible.
Customers who used the transaction WRY prior to Release 4.0 must make
a transfer posting from the WRY account to the WRX account in order to
ensure that the final balance on the WRY account is zero.