This is the second post of this ALE tutorial series. In order to make some progress, I will give an example to guide you how to configure, test your first ALE example. Please consider below example. There are two systems: system A and system B. We would like send material master in system A to system B using ALE/IDoc. Below is the system diagram.
In this series of posts, I try to provide a step by step tutorial on SAP ALE/IDoc. SAP provides a comprehensive documents in the help portal but I think it good for reference but not for beginners. It will be easier to have a step by step tutorial with screenshot. In the first post, I will give some explanation some abbreviations related to ALE/IDoc. Most of them come from SAP help portal. Please find the link in the reference section of this post.
ALE
Application Link Enabling (ALE) is a technology to create and run distributed applications. It comprises the controlled exchange of business messages and consistent data management in loosely-linked SAP application systems.
Application Link Enabling has three layers:
· Application services
· Distribution services
· Communication services
EDI
You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor). The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12). This enables communication with non-SAP systems.
Terms of payment is the key for defining payment term composed of cash discount percentages and payment period. It is maintained in the customer and vendor master record. The system will automatically defaults this key whenever you enter an item for this customer or vendor.
The payment term determines the valid cash discount rate for an individual payment with a maximum of 3 payment terms (first cash discount period, second cash discount period and due date for net payment) and also a baseline date for the payment. Below is the terms of payment configuration path.
|
Path |
Financial Accounting – Accounts Receivable and Accounts Payable – Business Transactions – Outgoing Invoices/Credit Memos – Maintain Terms of Payment |
|
T-code |
OBB8 |
Choose standard terms of payment AD10 for an example.
Purpose
Record the scrapping process for the material that the quality has been reduced due to long storage time or the material has been destroyed. In these cases, you need to post a scrapping. Below is the actual scrapping process in a manufacturing company.
Summary
Generally, there are two parts for this process.
1) Move the scrap material to scrap storage location and block it. In this step, the total stock number isn’t changed. Only the storage location and status is updated.
2) Post the scrapping. Material stock is reduced and an accounting document is generated.
In the output of SAP smartforms, the format of date and decimal point is determined by the country and user setting according to how print program and smartform developed. Below explains how SAP standard configuration to handle this format issue.
1. Country Format Setting
Go to tcode – OY01 and select country ‘US’ for example.
2. Standard print program for billing document – RLB_INVOICE
routine entry is the first routine called. In this routine, routine processing will be called. In routine processing, billing destination country will be retrieved in subroutine get_data. I didn’t check more detail logic but I think database field VBRK-LAND1 contains this information.
Once this value is retrieved, it will call subroutine set_print_param and passed in this parameter. In this routine. function module WFMC_PREPARE_SMART_FORM will be called.
In this function module, below statement will be executed.
SET COUNTRY pi_country.Below is the explanation from SAP help.
SET COUNTRY cntry.
This statement sets the formatting settings of the langauge environment for all subsequent statements of the current internal session. For cntry you must specify a character-like data object that either contains a value from the LAND column of the database table T005X or is initial.
If the content of cntry is neither found in the database table T005X nor contains a blank space in the first position, then sy-subrc is set to 4 and the following settings are made:
|
As long as the SET COUNTRY statement has not been carried out in an internal session, the formatting corresponds to the fixed values in the user master record.
SAP Consignment in MM module is similar with the consignment in sales process.
The process of MM consignment is very simple.
System generates consignment purchase requisition.(On the material master record, set special procurement indicator to 10 (consignment) at MRP2 view.)
The user transfer purchase requistition to consignment purchase order which item category is K.
The next is to process goods receipt to vendor consigment stock with movement type 103 or 105.
To consume vendor consigment stock,movement type 411+k is standard chosen.
In standard processing,there is no solution to vendor consignment return.
Movement type is a classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).
The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.
601 Goods issue for delivery (Shipping)
In Shipping, this movement type is created automatically with the Goods issue for delivery function. The quantity is taken from unrestricted-use stock.
REPORT ZPERIOD. DATA: X_PERIOD LIKE T009B-POPER, X_YEAR LIKE CSSL-GJAHR. CALL FUNCTION 'DATE_TO_PERIOD_CONVERT' EXPORTING I_DATE = SY-DATUM * I_MONMIT = 00 I_PERIV = 'K4' IMPORTING E_BUPER = X_PERIOD E_GJAHR = X_YEAR EXCEPTIONS INPUT_FALSE = 1 T009_NOTFOUND = 2 T009B_NOTFOUND = 3 OTHERS = 4. WRITE: / 'Your Company Current Period', X_PERIOD, X_YEAR. *-- End of Program
Non-deductible taxes are taxes that are not allowable when calculating a taxable income. They are taxes that have been paid in the process of generating income or purchasing items, but they are not subtracted from the final taxable income. For example,
VAT 14% non-deductible 50%
100 EUR invoice (account 5080)
7 EUR VAT goes to the VAT account
7 EUR VAT goes back to the Expense account (5080)
Total invoice 107.00
Total VAT 7.00
How to configuration this scenario in SAP?
In Tax code A2, Enter 7% in condition type MWAS and 7% in condition type MWVZ.
This post tries to give a comprehensive guide on SAP FI Tax configuration. Base configuration path in SPRO is SAP Customizing Implementation Guide –> Financial Accounting (New) –> Financial Accounting Global Settings (New) –> Tax on Sales/Purchases. SAP provides pre-defined tax related settings. Below steps just show you how to configuration tax for a new country if necessary.
Step 1. Check Calculation Procedure
Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries. Every calculation procedure groups several tax types together into a condition type (for example, output tax or input tax) in the calculation procedure, and determines calculation rules for it. Below screenshot shows the tax procedure TAXD. Read more…