At times some incorrect documents might have been entered in the systems. If you have entered an incorrect document, you can reverse it. Note that R/3 can reverse a document only if the following conditions are met: - Contains no cleared items - Contains only vendor, customer, or G/L line items - Was posted within the FI system - Contains only valid values, such as business areas, cost centers, and tax codes Ordinarily, you post a reversing document in the same period you posted the original document. The period of the original document must be open to post a reversing document. If the period is not open, you can overwrite the posting date field with a date in an open period, such as the current period. Reversal can be done individually - FB08 or Mass F.80. If the document to be reveresed contain cleared items, then cleared item must be reset before the reversal of document.
read more...
Showing posts with label SD. Show all posts
Showing posts with label SD. Show all posts
10.19.2008
Sales and Distribution Accounting Entries
Post under
SD
INVOICE GENERATION
Invoices will be generated at the Smelters and stock points. The accounting entries for the sale of goods despatched will flow from the Sales invoice generated in SAP Sales and Distribution module. The following entries shall be passed
Customer Account Dr
Revenue Cr
Excise Duty Payable Cr
Sales Tax Payable (local or central) Cr
Note: As mentioned above in the FI document, which is created in the background, the SD invoice number shall be captured. However as per the current accounting procedure the accounting entry passed is as follows :-
Customer Account Dr
Revenue Cr
Excise Duty Billed Cr
Sales Tax Payable (local or central) Cr
Excise duty paid a/c Dr
Excise duty payable a/c Cr
EXPORT SALES
There have been very few export transactions in the past. SAP system will be designed to handle export business. Exports are mainly from the mines and will be handled at the mines, however the documentation part will be taken care at the Head Office. The accounting entry is:
Customer Account Dr
Revenue (Exports) Cr
The realisation of export sales will be directly credited to the bank. The accounting entries will be as follow:
Bank Dr
Customer Cr
Exchange Fluctuation Dr/ Cr
The accounting entries will be:
Rebates/Discounts Dr
Customer
Cr
DEBIT MEMOS
Debit Memos shall be issued in case of price difference, sale tax difference and interest on usance period and overdue payments.
The accounting entries for two possible scenarios are as follows:
Price Undercharged:
Customer Account Dr.
Revenue Cr.
Sales tax payable Cr.
Sales tax undercharged
Customer Account Dr.
Sales tax adjustment Cr.
Interest on delayed payments/usance period and other charges
Customer Account Dr.
Interest Others Cr.
In case of HZL a complete retirement or a partial retirement of asset is done. The system uses the asset retirement date to determine the amount to be charged off for each depreciation area. The existing accounting policy is to provide depreciation for the full quarter in which the asset is sold/discarded, recommended that the depreciation be provided from the date of acquisition on prorata basis .
Accounting entry for sale of Asset to customers:
Customer Account Dr
Asset Sale Cr
Accumulated Depreciation Dr
Loss on Sale (if applicable) Dr
Asset Sale account Dr
Asset account Cr
Profit on sale (if applicable) Cr
Note: In case of any Sales Tax /Excise duty applicable for this transaction, SAP will calculate the Sales Tax/Excise Duty based on the Tax Code selected the entry is posted to the GL Account (Sales Tax Payable)
Accounting entry for sale without a customer:
Accumulated Depreciation Dr
Loss on Sale (if applicable) Dr
Asset Sale account Dr
Asset account Cr
Profit on sale (if applicable) Cr
Accounting entry for scrap
Accumulated Depreciation Dr
Loss on Sale of Assets Dr
Asset account Cr
SALE OF SCRAP
The sale of scrap (non-stock) shall be mapped as a direct manual FI entry. The customer will be created as a FI customer. No Logistics module will be involved in the process.
A FI Invoice will be prepared for the sale of scrap with the following entries:
Customer Dr
Sale of Scrap Cr
Excise Duty Payable Cr
ADVANCES FROM CUSTOMERS
Advances are received from the customers against delivery. These advances will be recorded in a special general ledger account. The accounting entry for the same will be:
Bank Account Dr
Advance Customer Payments Cr
These advances will be later on adjusted against the invoices raised on the customers. Advances can be adjusted against more than one invoice at the time of clearing of the invoices against advances.
Adjustment of Advances
Customer Account Cr
Advance Customer Payments Dr
A financial document would be created for each Bank Guarantee received and this document number will be referred to in the Sales Order which would then monitor the value and the validity of the of the Bank Guarantee instrument wise while doing the billing.The letter of credit /Bank guarantee given will be recorded as a noted item.
Accounting Entry for Goods receipt
Stock/Inventory account Dr
GR/IR account Cr
Freight clearing account Cr
Accounting Entry on invoice verification of supplier
GR/IR Dr
Vendor account Cr
Accounting Entry on invoice verification of freight vendor
Freight clearing account Dr
Freight Vendor account Cr
GOODS RECEIPT
Based on the Purchase order and the Quantity actually received Goods Receipts (GR) will be done. Based on the GR done the following accounting entry will be passed in the Financial Accounts
RM/PM Stock Account Dr
GR/IR Account Cr
Freight Clearing Account Cr
EXCISE INVOICE VERIFICATION
On receipt of the excise invoice cum gate pass the following entry will be passed
RG 23 A / RG 23 C Part 2 Account Dr
Cenvat Clearing Account Cr
read more...
Invoices will be generated at the Smelters and stock points. The accounting entries for the sale of goods despatched will flow from the Sales invoice generated in SAP Sales and Distribution module. The following entries shall be passed
Customer Account Dr
Revenue Cr
Excise Duty Payable Cr
Sales Tax Payable (local or central) Cr
Note: As mentioned above in the FI document, which is created in the background, the SD invoice number shall be captured. However as per the current accounting procedure the accounting entry passed is as follows :-
Customer Account Dr
Revenue Cr
Excise Duty Billed Cr
Sales Tax Payable (local or central) Cr
Excise duty paid a/c Dr
Excise duty payable a/c Cr
EXPORT SALES
There have been very few export transactions in the past. SAP system will be designed to handle export business. Exports are mainly from the mines and will be handled at the mines, however the documentation part will be taken care at the Head Office. The accounting entry is:
Customer Account Dr
Revenue (Exports) Cr
The realisation of export sales will be directly credited to the bank. The accounting entries will be as follow:
Bank Dr
Customer Cr
Exchange Fluctuation Dr/ Cr
The accounting entries will be:
Rebates/Discounts Dr
Customer
Cr
DEBIT MEMOS
Debit Memos shall be issued in case of price difference, sale tax difference and interest on usance period and overdue payments.
The accounting entries for two possible scenarios are as follows:
Price Undercharged:
Customer Account Dr.
Revenue Cr.
Sales tax payable Cr.
Sales tax undercharged
Customer Account Dr.
Sales tax adjustment Cr.
Interest on delayed payments/usance period and other charges
Customer Account Dr.
Interest Others Cr.
In case of HZL a complete retirement or a partial retirement of asset is done. The system uses the asset retirement date to determine the amount to be charged off for each depreciation area. The existing accounting policy is to provide depreciation for the full quarter in which the asset is sold/discarded, recommended that the depreciation be provided from the date of acquisition on prorata basis .
Accounting entry for sale of Asset to customers:
Customer Account Dr
Asset Sale Cr
Accumulated Depreciation Dr
Loss on Sale (if applicable) Dr
Asset Sale account Dr
Asset account Cr
Profit on sale (if applicable) Cr
Note: In case of any Sales Tax /Excise duty applicable for this transaction, SAP will calculate the Sales Tax/Excise Duty based on the Tax Code selected the entry is posted to the GL Account (Sales Tax Payable)
Accounting entry for sale without a customer:
Accumulated Depreciation Dr
Loss on Sale (if applicable) Dr
Asset Sale account Dr
Asset account Cr
Profit on sale (if applicable) Cr
Accounting entry for scrap
Accumulated Depreciation Dr
Loss on Sale of Assets Dr
Asset account Cr
SALE OF SCRAP
The sale of scrap (non-stock) shall be mapped as a direct manual FI entry. The customer will be created as a FI customer. No Logistics module will be involved in the process.
A FI Invoice will be prepared for the sale of scrap with the following entries:
Customer Dr
Sale of Scrap Cr
Excise Duty Payable Cr
ADVANCES FROM CUSTOMERS
Advances are received from the customers against delivery. These advances will be recorded in a special general ledger account. The accounting entry for the same will be:
Bank Account Dr
Advance Customer Payments Cr
These advances will be later on adjusted against the invoices raised on the customers. Advances can be adjusted against more than one invoice at the time of clearing of the invoices against advances.
Adjustment of Advances
Customer Account Cr
Advance Customer Payments Dr
A financial document would be created for each Bank Guarantee received and this document number will be referred to in the Sales Order which would then monitor the value and the validity of the of the Bank Guarantee instrument wise while doing the billing.The letter of credit /Bank guarantee given will be recorded as a noted item.
Accounting Entry for Goods receipt
Stock/Inventory account Dr
GR/IR account Cr
Freight clearing account Cr
Accounting Entry on invoice verification of supplier
GR/IR Dr
Vendor account Cr
Accounting Entry on invoice verification of freight vendor
Freight clearing account Dr
Freight Vendor account Cr
GOODS RECEIPT
Based on the Purchase order and the Quantity actually received Goods Receipts (GR) will be done. Based on the GR done the following accounting entry will be passed in the Financial Accounts
RM/PM Stock Account Dr
GR/IR Account Cr
Freight Clearing Account Cr
EXCISE INVOICE VERIFICATION
On receipt of the excise invoice cum gate pass the following entry will be passed
RG 23 A / RG 23 C Part 2 Account Dr
Cenvat Clearing Account Cr
9.08.2008
How To Do Configuration For Credit Management
Post under
ABAP Transactions,
MM,
SD
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
read more...
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
8.12.2008
Standard SAP SD Reports
Post under
SD
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
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
read more...
Sales summary - VC/2
Display Customer Hierarchy - VDH2
Display Condition record report - V/I6
Pricing Report - V/LD
Create Net Price List - V_NL
List customer material info - VD59
List of sales order - VA05
List of Billing documents - VF05
Inquiries list - VA15
Quotation List - VA25
Incomplete Sales orders - V.02
Backorders - V.15
Outbound Delivery Monitor - VL06o
Incomplete delivery - V_UC
Customer Returns-Analysis - MC+A
Customer Analysis- Sales - MC+E
Customer Analysis- Cr. Memo - MC+I
Deliveries-Due list - VL04
Billing due list - VF04
Incomplete Billing documents - MCV9
Customer Analysis-Basic List - MCTA
Material Analysis(SIS) - MCTC
Sales org analysis - MCTE
Sales org analysis-Invoiced sales - MC+2
Material Analysis-Incoming orders - MC(E
General- List of Outbound deliveries - VL06f
Material Returns-Analysis - MC+M
Material Analysis- Invoiced Sales - MC+Q
Variant configuration Analysis - MC(B
Sales org analysis-Incoming orders - MC(I
Sales org analysis-Returns - MC+Y
Sales office Analysis- Invoiced Sales - MC-E
Sales office Analysis- Returns - MC-A
Shipping point Analysis - MC(U
Shipping point Analysis-Returns - MC-O
Blocked orders - V.14
Order Within time period - SD01
Duplicate Sales orders in period - SDD1
Display Delivery Changes - VL22
8.06.2008
SAP SD transaction codes
Post under
SD
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
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
read more...
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
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
8.02.2008
Generic Withholding Tax Reporting
Post under
SD
· Select Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax General -> S_P00_07000134.
Transaction Code
S_P00_07000134
Tips and Tricks
· If you cannot see the S_P00_07000134 transaction code by the description "Generic Withholding Tax Reporting", do the following steps:
0.1 From the SAP Easy Access menu, from the menu toolbar at the top of the screen, click on Extras -> Setting or click on Shift + F9. The following screen will appear:
Technical Settings
0.2 Check
the "Display technical names" check box.
0.3 Click to continue and the SAP Easy Access menu will be reset.
· Select Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax General -> S_P00_07000134.
Transaction Code
S_P00_07000134
Tips and Tricks
· If you cannot see the S_P00_07000134 transaction code by the description "Generic Withholding Tax Reporting", do the following steps:
0.1 From the SAP Easy Access menu, from the menu toolbar at the top of the screen, click on Extras -> Setting or click on Shift + F9. The following screen will appear:
Technical Settings
0.2 Checkthe "Display technical names" check box.
0.3 Click to continue and the SAP Easy Access menu will be reset.
· If you know the transaction code (t-code) then you may type the code in the entry box in the upper left-hand corner of the SAP Easy Access screen and hit the Enter Key or
icon to proceed.
You can save this transaction to your Favorites list by going to the SAP Easy Access window and left-clicking on the Transaction code. While holding the mouse button down, drag it to the top of the window into the Favorites folder.
· Create your own variant if the variant in this demo does not meet your needs.
· To navigate a report with multiple pages, utilize these buttons:
. The first takes you to the first page. The second takes you to the previous page. The third takes you to the next page. The fourth takes you to the last page.
Procedure
Your Favorites folder may have different t-codes saved. Ignore the Favorites folder of the above menu path.
read more...
Transaction Code
S_P00_07000134
Tips and Tricks
· If you cannot see the S_P00_07000134 transaction code by the description "Generic Withholding Tax Reporting", do the following steps:
0.1 From the SAP Easy Access menu, from the menu toolbar at the top of the screen, click on Extras -> Setting or click on Shift + F9. The following screen will appear:
Technical Settings
0.2 Check
the "Display technical names" check box.0.3 Click to continue and the SAP Easy Access menu will be reset.
· Select Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax General -> S_P00_07000134.
Transaction Code
S_P00_07000134
Tips and Tricks
· If you cannot see the S_P00_07000134 transaction code by the description "Generic Withholding Tax Reporting", do the following steps:
0.1 From the SAP Easy Access menu, from the menu toolbar at the top of the screen, click on Extras -> Setting or click on Shift + F9. The following screen will appear:
Technical Settings
0.2 Check
the "Display technical names" check box.0.3 Click to continue and the SAP Easy Access menu will be reset.
· If you know the transaction code (t-code) then you may type the code in the entry box in the upper left-hand corner of the SAP Easy Access screen and hit the Enter Key or
icon to proceed.
You can save this transaction to your Favorites list by going to the SAP Easy Access window and left-clicking on the Transaction code. While holding the mouse button down, drag it to the top of the window into the Favorites folder.
· Create your own variant if the variant in this demo does not meet your needs.
· To navigate a report with multiple pages, utilize these buttons:
. The first takes you to the first page. The second takes you to the previous page. The third takes you to the next page. The fourth takes you to the last page.Procedure
Your Favorites folder may have different t-codes saved. Ignore the Favorites folder of the above menu path.
7.31.2008
What is Data Archieving and its procedure?
Post under
SD
Right Retrieval Strategy
An important challenge for SAP administrators is to find out the appropriate data for archiving. It is important to have knowledge of the business processes involved in the enterprise, prior to data archiving, so that appropriate archive objects are created. This helps in identifying database table growth and simplifies the process of identifying objects for archiving.
Three Phase Archiving Process
Data archiving process comprises three major phases. They are:
* Creating an archive file
* Removing the archived data from the database
* Transferring the archived files to a location outside the SAP database
Currently, a large number of enterprises use SAP R/3 as a platform for integration of business processes. The continuous usage of SAP results in huge amounts of enterprise data, which is stored in SAP R/3. With passage of time, the new and updated data is entered into the system while the old data still resides in the SAP enterprise system.
Since some of the old data is critical, it cannot be deleted. The difficulty is keeping the data you want, and deleting the data you do not want. Hence, a SAP database keeps on expanding rapidly and enterprise systems, which have limited data retention abilities for a few years, suffer from problems such as data overflow, longer transaction processing times, and performance degradation.
The solution of this problem has led to the concept of Data Archiving in SAP. Data Archiving removes out-of-date data from the SAP database that the R/3 system does not need online, but can be retrieved on a later date, if required. This data is known as archived data and is stored at an offline location. Data Archiving not only consistently removes data from the database but also ensures data availability for future business requirements.
One rule of thumb is that in a typical SAP enterprise system, the ratio of data required to be online and instantly accessible to old data, which could be archived, and stored offline is 1:6. For example, if an enterprise has 2100 GB of SAP database, the online data, which is frequently used by SAP users will be 300 MB and the rest (1800 MB) will be scarcely used and hence can be archived.
Data Archiving – Features
* It provides a protection layer to the SAP database and resolves underperformance problems caused by huge volumes of data. It is important that SAP users should keep only minimal data to efficiently work with database and servers. Data archiving ensures that the SAP database contains only relevant and up-to-date data that meet your requirements.
* Data archiving uses hardware components such as hard disks and memory. For efficient data archiving, minimum number of disks and disk space should be used.
* It also reduces the system maintenance costs associated with the SAP database. In the SAP database there are various procedures such as, data backup, data recovery, and data upgrade.
# SAP data archiving complies with statutory data retention rules that are common and well-proven techniques.
Right Retrieval Strategy
read more...
An important challenge for SAP administrators is to find out the appropriate data for archiving. It is important to have knowledge of the business processes involved in the enterprise, prior to data archiving, so that appropriate archive objects are created. This helps in identifying database table growth and simplifies the process of identifying objects for archiving.
Three Phase Archiving Process
Data archiving process comprises three major phases. They are:
* Creating an archive file
* Removing the archived data from the database
* Transferring the archived files to a location outside the SAP database
Currently, a large number of enterprises use SAP R/3 as a platform for integration of business processes. The continuous usage of SAP results in huge amounts of enterprise data, which is stored in SAP R/3. With passage of time, the new and updated data is entered into the system while the old data still resides in the SAP enterprise system.
Since some of the old data is critical, it cannot be deleted. The difficulty is keeping the data you want, and deleting the data you do not want. Hence, a SAP database keeps on expanding rapidly and enterprise systems, which have limited data retention abilities for a few years, suffer from problems such as data overflow, longer transaction processing times, and performance degradation.
The solution of this problem has led to the concept of Data Archiving in SAP. Data Archiving removes out-of-date data from the SAP database that the R/3 system does not need online, but can be retrieved on a later date, if required. This data is known as archived data and is stored at an offline location. Data Archiving not only consistently removes data from the database but also ensures data availability for future business requirements.
One rule of thumb is that in a typical SAP enterprise system, the ratio of data required to be online and instantly accessible to old data, which could be archived, and stored offline is 1:6. For example, if an enterprise has 2100 GB of SAP database, the online data, which is frequently used by SAP users will be 300 MB and the rest (1800 MB) will be scarcely used and hence can be archived.
Data Archiving – Features
* It provides a protection layer to the SAP database and resolves underperformance problems caused by huge volumes of data. It is important that SAP users should keep only minimal data to efficiently work with database and servers. Data archiving ensures that the SAP database contains only relevant and up-to-date data that meet your requirements.
* Data archiving uses hardware components such as hard disks and memory. For efficient data archiving, minimum number of disks and disk space should be used.
* It also reduces the system maintenance costs associated with the SAP database. In the SAP database there are various procedures such as, data backup, data recovery, and data upgrade.
# SAP data archiving complies with statutory data retention rules that are common and well-proven techniques.
Right Retrieval Strategy
An important challenge for SAP administrators is to find out the appropriate data for archiving. It is important to have knowledge of the business processes involved in the enterprise, prior to data archiving, so that appropriate archive objects are created. This helps in identifying database table growth and simplifies the process of identifying objects for archiving.
Data archiving process comprises three major phases. They are:
- Creating an archive file
- Removing the archived data from the database
- Transferring the archived files to a location outside the SAP database
Phase I - Creating Archive Files
The archived files of data are created in the SAP database by the Archiving Management system. The Management system reads the data from the database and writes it to the archive files in the background. In instances of archived files exceeding the maximum specified limit, or if the number of data objects exceed the stipulated limit in the system, then the system automatically creates new archive files.
At the end of the process of saving data into archive files, ADK triggers the system event SAP_ARCHIVING_WRITE_FINISHED, which is an indicator to the system to start next phase of archiving process.
Phase II - Deleting files from the Database
While archiving management system writes data on the archive files, another program deletes it from the database permanently. The program checks whether the data has been transferred to the archive. It is quite important too as it is the last check performed by the system before deleting data permanently from the database. Several deletion programs run simultaneously, because the archiving program is much more faster than the deletion programs. This is important as it increases the efficiency of archiving process.
Phase III - Transferring Archive Files
Once the Archive management system has finished archiving the data, the next step is to save the archived files at a different location other than the SAP database. This can be accomplished by an automated process in the system or by a manual process. This step is optional since many enterprises may wish to keep the archived files within the current database. However, large enterprises transfer their data periodically as a part of their data archiving processes.
What is Forward and Backward Scheduling?
Post under
SD
Precise scheduling calculated down to the day, hour and minute is supported. This allows the scheduling of a delivery within a single day. It is activated by maintaining the working hours for a particular shipping point.
Backward scheduling is always carried out first. If the material availability date or transportation scheduling date is calculated to be in the past, the system must then use forward scheduling.
Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities. The loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date.
Backward scheduling is the calculation of deadline dates: the arrival time at the customer site is calculated as the earliest possible goods receipt time at the customers unloading point on the requested delivery date. All four of the delivery and transportation scheduling lead times are subtracted from the customer’s requested delivery date to determine if this date can be met.
The transit time, loading time, and pick/pack time are subtracted from the customer’s requested delivery date to calculate the required material availability date.
The system calculates backward scheduling as follows:
Requested delivery date minus transit time = Goods issue date
Goods issue date minus loading time = Loading date
Loading date minus transportation lead time = Transportation scheduling date
Loading date minus pick/pack time = Material availability date
By default, the system will calculate delivery dates the closest day, taking into consideration the working days of the shipping point and a rounding profile. In this case the system assumes a 24 hour work day and lead times can be entered in days up to 2 decimal points. This is referred to as daily scheduling.
Precise scheduling calculated down to the day, hour and minute is supported. This allows the scheduling of a delivery within a single day. It is activated by maintaining the working hours for a particular shipping point.
Backward scheduling is always carried out first. If the material availability date or transportation scheduling date is calculated to be in the past, the system must then use forward scheduling.
Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities. The loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date.
read more...
Backward scheduling is always carried out first. If the material availability date or transportation scheduling date is calculated to be in the past, the system must then use forward scheduling.
Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities. The loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date.
Backward scheduling is the calculation of deadline dates: the arrival time at the customer site is calculated as the earliest possible goods receipt time at the customers unloading point on the requested delivery date. All four of the delivery and transportation scheduling lead times are subtracted from the customer’s requested delivery date to determine if this date can be met.
The transit time, loading time, and pick/pack time are subtracted from the customer’s requested delivery date to calculate the required material availability date.
The system calculates backward scheduling as follows:
Requested delivery date minus transit time = Goods issue date
Goods issue date minus loading time = Loading date
Loading date minus transportation lead time = Transportation scheduling date
Loading date minus pick/pack time = Material availability date
By default, the system will calculate delivery dates the closest day, taking into consideration the working days of the shipping point and a rounding profile. In this case the system assumes a 24 hour work day and lead times can be entered in days up to 2 decimal points. This is referred to as daily scheduling.
Precise scheduling calculated down to the day, hour and minute is supported. This allows the scheduling of a delivery within a single day. It is activated by maintaining the working hours for a particular shipping point.
Backward scheduling is always carried out first. If the material availability date or transportation scheduling date is calculated to be in the past, the system must then use forward scheduling.
Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities. The loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date.
SD - Finance Table
AGKO Cleared Accounts
ANAR Asset Types
ANAT Asset type text
ANEK Document Header Asset Posting
ANEP Asset Line Items
ANEV Asset downpymt settlement
ANKT Asset classes- Description
ANLA Asset Master Record Segment
ANLB Depreciation terms
ANLC Asset Value Fields
ANLH Main asset number
AT02T Transaction Activity Category- Description
AT02A Transaction Code for Menu TIMN...........
AGKO Cleared Accounts
ANAR Asset Types
ANAT Asset type text
ANEK Document Header Asset Posting
ANEP Asset Line Items
ANEV Asset downpymt settlement
ANKT Asset classes- Description
ANLA Asset Master Record Segment
ANLB Depreciation terms
ANLC Asset Value Fields
ANLH Main asset number
AT02T Transaction Activity Category- Description
AT02A Transaction Code for Menu TIMN
AT10 Transaction type
AT10T Name of Transaction Type
BKDF Document Header Supplement for Recurring Entry
BKORM Accounting Correspondence Requests
BKPF Accounting Document Header
BLPK Document log header
BLPP Document log item
BLPR Document Log Index and Planned Order (Backflush)
BNKA Bank master record
BP000 Business Partner Master (General Data)
BPBK Doc.Header Controlling Obj.
BPEG Line Item Total Values Controlling Obj.
BPEJ Line Item Annual Values Controlling Obj.
BPEP Line Item Period Values Controlling Obj.
BPGE Totals Record for Total Value Controlling obj.
BPJA Totals Record for Annual Total Controlling Obj.
BSAD Accounting- Secondary Index for Customers (Cleared Items)
BSAK Accounting- Secondary Index for Vendors (Cleared Items)
BSAS Accounting- Secondary Index for G/L Accounts (Cleared Items)
BSEC One-Time Account Data Document Segment
BSEG Accounting Document Segment
BSID Accounting- Secondary Index for Customers
BSIK Accounting- Secondary Index for Vendors
BSIM Secondary Index, Documents for Material
BSIS Accounting- Secondary Index for G/L Accounts
CEPC Profit Center Master Data Table
CEPCT Texts for Profit Center Master Data
COBRA Settlement Rule for Order Settlement
COBRB Distribution Rules Settlement Rule Order Settlement
COKA CO Object- Control Data for Cost Elements
COSP CO Object- Cost Totals for External Postings
COSS CO Object- Cost Totals for Internal Postings
CRCO Assignment of Work Center to Cost Center
CSKA Cost Elements (Data Dependent on Chart of Accounts)
CSKB Cost Elements (Data Dependent on Controlling Area)
CSLA Activity master
FEBEP Electronic Bank Statement Line Items
FPLA Billing Plan
FPLT Billing Plan- Dates
GLPCT EC-PCA- Totals Table
KNA1 General Data in Customer Master
KOMK Pricing Communication Header
MAHNV Management Records for the Dunning Program
REGUT TemSe - Administration Data
SKA1 G/L Account Master (Chart of Accounts)
SKAT G/L Account Master Record (Chart of Accounts- Description)
SKB1 G/L account master (company code)
T003T Document Type Texts
T007S Tax Code Names
T087J Text
TAPRFT Text tab. for investment profile
TKA01 Controlling Areas
TKA09 Basic Settings for Versions
TKVS CO Versions
TZB0T Flow types text table
TZPAT Financial Assets Management product type texts
VBSEGS Document Segment for G/L Accounts Document Parking
VTBFHA Transaction
VTBFHAPO Transaction Flow
VTBFHAZU Transaction Activity
VTBFINKO Transaction Condition
VTIDERI Master Data Listed Options and Futures
VTIFHA Underlying transaction
VTIFHAPO Underlying transaction flows
VTIFHAZU Underlying transaction status table
VTIOF Options Additional Data
VWPANLA Asset master for securities
read more...
ANAR Asset Types
ANAT Asset type text
ANEK Document Header Asset Posting
ANEP Asset Line Items
ANEV Asset downpymt settlement
ANKT Asset classes- Description
ANLA Asset Master Record Segment
ANLB Depreciation terms
ANLC Asset Value Fields
ANLH Main asset number
AT02T Transaction Activity Category- Description
AT02A Transaction Code for Menu TIMN...........
AGKO Cleared Accounts
ANAR Asset Types
ANAT Asset type text
ANEK Document Header Asset Posting
ANEP Asset Line Items
ANEV Asset downpymt settlement
ANKT Asset classes- Description
ANLA Asset Master Record Segment
ANLB Depreciation terms
ANLC Asset Value Fields
ANLH Main asset number
AT02T Transaction Activity Category- Description
AT02A Transaction Code for Menu TIMN
AT10 Transaction type
AT10T Name of Transaction Type
BKDF Document Header Supplement for Recurring Entry
BKORM Accounting Correspondence Requests
BKPF Accounting Document Header
BLPK Document log header
BLPP Document log item
BLPR Document Log Index and Planned Order (Backflush)
BNKA Bank master record
BP000 Business Partner Master (General Data)
BPBK Doc.Header Controlling Obj.
BPEG Line Item Total Values Controlling Obj.
BPEJ Line Item Annual Values Controlling Obj.
BPEP Line Item Period Values Controlling Obj.
BPGE Totals Record for Total Value Controlling obj.
BPJA Totals Record for Annual Total Controlling Obj.
BSAD Accounting- Secondary Index for Customers (Cleared Items)
BSAK Accounting- Secondary Index for Vendors (Cleared Items)
BSAS Accounting- Secondary Index for G/L Accounts (Cleared Items)
BSEC One-Time Account Data Document Segment
BSEG Accounting Document Segment
BSID Accounting- Secondary Index for Customers
BSIK Accounting- Secondary Index for Vendors
BSIM Secondary Index, Documents for Material
BSIS Accounting- Secondary Index for G/L Accounts
CEPC Profit Center Master Data Table
CEPCT Texts for Profit Center Master Data
COBRA Settlement Rule for Order Settlement
COBRB Distribution Rules Settlement Rule Order Settlement
COKA CO Object- Control Data for Cost Elements
COSP CO Object- Cost Totals for External Postings
COSS CO Object- Cost Totals for Internal Postings
CRCO Assignment of Work Center to Cost Center
CSKA Cost Elements (Data Dependent on Chart of Accounts)
CSKB Cost Elements (Data Dependent on Controlling Area)
CSLA Activity master
FEBEP Electronic Bank Statement Line Items
FPLA Billing Plan
FPLT Billing Plan- Dates
GLPCT EC-PCA- Totals Table
KNA1 General Data in Customer Master
KOMK Pricing Communication Header
MAHNV Management Records for the Dunning Program
REGUT TemSe - Administration Data
SKA1 G/L Account Master (Chart of Accounts)
SKAT G/L Account Master Record (Chart of Accounts- Description)
SKB1 G/L account master (company code)
T003T Document Type Texts
T007S Tax Code Names
T087J Text
TAPRFT Text tab. for investment profile
TKA01 Controlling Areas
TKA09 Basic Settings for Versions
TKVS CO Versions
TZB0T Flow types text table
TZPAT Financial Assets Management product type texts
VBSEGS Document Segment for G/L Accounts Document Parking
VTBFHA Transaction
VTBFHAPO Transaction Flow
VTBFHAZU Transaction Activity
VTBFINKO Transaction Condition
VTIDERI Master Data Listed Options and Futures
VTIFHA Underlying transaction
VTIFHAPO Underlying transaction flows
VTIFHAZU Underlying transaction status table
VTIOF Options Additional Data
VWPANLA Asset master for securities
Complete Transaction Set
Transactions
* search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
EDI Specific Transactions
* VOE1 - Translation between EDI categories and SD item categories
* VOE2 - Table EDSC view. Customer link to sales area detail
* VOE3 - Table view EDPVW. Add partner types that will be transferred to the IDoc
* VOE4 - Table view EDPAR. Link external partner number with our internal number
* WEDI- EDI Administrator Menu
* BALE - Idoc Administration
Scheduling agreements
* OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
Transactions
* search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
EDI Specific Transactions
* VOE1 - Translation between EDI categories and SD item categories
* VOE2 - Table EDSC view. Customer link to sales area detail
* VOE3 - Table view EDPVW. Add partner types that will be transferred to the IDoc
* VOE4 - Table view EDPAR. Link external partner number with our internal number
* WEDI- EDI Administrator Menu
* BALE - Idoc Administration
Scheduling agreements
* OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
*OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
* OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
IDoc Transactions
* WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
* WE05 View IDocs
* WE19 EDI test tool. Use to test inbound Function module changes.
* WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
* WE30 Create IDoc extension type
* WE31 Segment create
* WE57 Assign function module to logical message and IDoc type
* WE60 IDoc type documentation tool
* WE82 Link Release detail to Extension IDoc Type
* BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
* BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
* BALA ALE Application Distribution
* BALM ALE Master Data Distribution
Output determination
856 - ASN
* V/36 Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 – V7ALLE – SHAD for grouped ASNs. I.e. Group deliveries into shipments
* VV21,VV22,VV23 Create output condition records for shipping. LAVA – WE (Partner function) - We must add each new partner with VV21
* VL71 Reissue output for deliveries
810 - Invoice
* V/54 Maintain access sequence for billing documents
* VV31,VV32,VV33 Create condition records for billing documents. (RD00 – RE Billing party)
* VF31 Reissue output for billing documents
855 – Order Response
* V/30 Sales document output types (BA00)
* V/48, V/32, V/43 Maintain access sequence for sales documents
* VV11,VV12,VV13 Create condition records for sales documents. (BA00 – SP Sold to party)
requirements coding
* V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
* VA02 Sales order change
* VA05 List of sales orders
* VA22 Quotation change
* VA32 Scheduling agreement change
* VA42 Contract change
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
Workflow
* SWEAD Event queue administration
* SWE2 Event type linkages
* SWE3 Event linkages
* PPOME Organizational Unit Maintenance
* SWE5 Consistency Checks for Event Linkages
* SWUD Workflow Diagnostic Tool
General
The following section provides detail on other useful SAP areas.
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
* VL04 Delivery due list. Run the delivery due with your order number to create the delivery
* LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
* In LT03 go to menu option Transfer Order -> Confirm – Transfer Order
* Enter
* Save
The transfer order is now confirmed.
* VL02N Delivery change. EG: Edit the delivery to do the following Pack – External customer material number = COO. External delivery number – Waybill number. BOL – Transport tag. Carrier – Header partner – SP (E.G. FXP). Tracking number = Packing Unit
Purchase Orders
* ME22N PO Change
* ME57 Create PO from purchase requisition
ATP
* CO09 Availability overview
Goods Movement
* MIGO Post goods receipt
* MB51 Material document list
* MB01 Goods Movement
Other
* MD04 Material Requirements. Shows material requirements and releases against materials
* SE38 ABAP Editor. Used to modify ABAP programs
* SM01 Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
* SHDB Transaction recorder (BDC)
* CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
* SE16 Table contents display
* SOST View mails sent externally from SAP
* SU53 Check authorization object
* SQVI Table Quickviewer – Used to created quick client dependent reports
* ST22 ABAP Dump Analysis
* ST01 System trace
* ST11 Display developer trace
* ST05 SQL Trace
* SM21 System log
* ST22 Display short dumps
* SM12 Display locked entries
Programs
* List of ABAP Reports
Idoc
* RBDAPP01 Post inbound Idocs to application documents
* RBDAGAI2 Re-processing of IDocs after ALE input error
* RBDAGAIE Reprocessing of edited IDocs
* RBDMANIN Start error handling for non-posted Idocs
* RSEINB00 Idoc inbound processing by file
* RSEOUT00 Process outbound IDocs
General
* RV80HGEN Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.
* RSWUWFML Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status’ sent from SAP.
* RHSOBJCH Corrects the following error in workflow customizing:
Transport object PDST
Information Table SOBJ is consistent as regards key tables
***Error*** Table HRP1600 Not an entry in table SOBJ
Information Table SOBJ is consistent as regards PAD tables
See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.
* RSPO0075 Run report RSPO0075 to activate access method M for device types.
read more...
* search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
EDI Specific Transactions
* VOE1 - Translation between EDI categories and SD item categories
* VOE2 - Table EDSC view. Customer link to sales area detail
* VOE3 - Table view EDPVW. Add partner types that will be transferred to the IDoc
* VOE4 - Table view EDPAR. Link external partner number with our internal number
* WEDI- EDI Administrator Menu
* BALE - Idoc Administration
Scheduling agreements
* OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
Transactions
* search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
EDI Specific Transactions
* VOE1 - Translation between EDI categories and SD item categories
* VOE2 - Table EDSC view. Customer link to sales area detail
* VOE3 - Table view EDPVW. Add partner types that will be transferred to the IDoc
* VOE4 - Table view EDPAR. Link external partner number with our internal number
* WEDI- EDI Administrator Menu
* BALE - Idoc Administration
Scheduling agreements
* OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
*OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
* OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
IDoc Transactions
* WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
* WE05 View IDocs
* WE19 EDI test tool. Use to test inbound Function module changes.
* WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
* WE30 Create IDoc extension type
* WE31 Segment create
* WE57 Assign function module to logical message and IDoc type
* WE60 IDoc type documentation tool
* WE82 Link Release detail to Extension IDoc Type
* BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
* BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
* BALA ALE Application Distribution
* BALM ALE Master Data Distribution
Output determination
856 - ASN
* V/36 Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 – V7ALLE – SHAD for grouped ASNs. I.e. Group deliveries into shipments
* VV21,VV22,VV23 Create output condition records for shipping. LAVA – WE (Partner function) - We must add each new partner with VV21
* VL71 Reissue output for deliveries
810 - Invoice
* V/54 Maintain access sequence for billing documents
* VV31,VV32,VV33 Create condition records for billing documents. (RD00 – RE Billing party)
* VF31 Reissue output for billing documents
855 – Order Response
* V/30 Sales document output types (BA00)
* V/48, V/32, V/43 Maintain access sequence for sales documents
* VV11,VV12,VV13 Create condition records for sales documents. (BA00 – SP Sold to party)
requirements coding
* V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
* VA02 Sales order change
* VA05 List of sales orders
* VA22 Quotation change
* VA32 Scheduling agreement change
* VA42 Contract change
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
Workflow
* SWEAD Event queue administration
* SWE2 Event type linkages
* SWE3 Event linkages
* PPOME Organizational Unit Maintenance
* SWE5 Consistency Checks for Event Linkages
* SWUD Workflow Diagnostic Tool
General
The following section provides detail on other useful SAP areas.
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
* VL04 Delivery due list. Run the delivery due with your order number to create the delivery
* LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
* In LT03 go to menu option Transfer Order -> Confirm – Transfer Order
* Enter
* Save
The transfer order is now confirmed.
* VL02N Delivery change. EG: Edit the delivery to do the following Pack – External customer material number = COO. External delivery number – Waybill number. BOL – Transport tag. Carrier – Header partner – SP (E.G. FXP). Tracking number = Packing Unit
Purchase Orders
* ME22N PO Change
* ME57 Create PO from purchase requisition
ATP
* CO09 Availability overview
Goods Movement
* MIGO Post goods receipt
* MB51 Material document list
* MB01 Goods Movement
Other
* MD04 Material Requirements. Shows material requirements and releases against materials
* SE38 ABAP Editor. Used to modify ABAP programs
* SM01 Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
* SHDB Transaction recorder (BDC)
* CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
* SE16 Table contents display
* SOST View mails sent externally from SAP
* SU53 Check authorization object
* SQVI Table Quickviewer – Used to created quick client dependent reports
* ST22 ABAP Dump Analysis
* ST01 System trace
* ST11 Display developer trace
* ST05 SQL Trace
* SM21 System log
* ST22 Display short dumps
* SM12 Display locked entries
Programs
* List of ABAP Reports
Idoc
* RBDAPP01 Post inbound Idocs to application documents
* RBDAGAI2 Re-processing of IDocs after ALE input error
* RBDAGAIE Reprocessing of edited IDocs
* RBDMANIN Start error handling for non-posted Idocs
* RSEINB00 Idoc inbound processing by file
* RSEOUT00 Process outbound IDocs
General
* RV80HGEN Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.
* RSWUWFML Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status’ sent from SAP.
* RHSOBJCH Corrects the following error in workflow customizing:
Transport object PDST
Information Table SOBJ is consistent as regards key tables
***Error*** Table HRP1600 Not an entry in table SOBJ
Information Table SOBJ is consistent as regards PAD tables
See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.
* RSPO0075 Run report RSPO0075 to activate access method M for device types.
Subscribe to:
Posts (Atom)
Popular Posts
-
Brides look incredibly beautiful. They are not looking back at the life they are leaving...they are looking the life they are entering, and...
-
Import Parameters Name and Description Field name Field function Object_hd_change (structure) Contains the process to be done whe...
-
1. What is ALE? Application Link Enabling (ALE) is a set of business processes and tools that allow applications on different computer syste...
-
Nowadays every computer professional having an option of work from Home. And many of us switched from desktop computers to Laptops. How do ... -
'SO_OBJECT_SEND' is to allow you send SAPOffice mails from within your ABAP programs. However, using that function module is complex...
