The Kind of SAP Tables
T**** Tables are Transparent Tables
Has a Physical definition and gets created in the database.
V_ Tables are View Tables
View tables are basically LOGICAL VIEW of one or more tables. For example a view is not actually physically stored, instead it is derived from one or more other tables… if you look at the View Table Structure.. you will see that they are basically JOINS of other tables and the fields are derived by varied tables…
Checking SAP Tables via SM30 transaction. eg:
- T512W_D (Definition/Has Physical Storage)
- V_512W_D (Table with Joins/doesnt have physical storage)
Viewed 17787 times by 4722 viewers
Travel Management: Travel Planning Processes
Travel Planning in SAP Travel Management with its integrated online booking service contributes greatly towards reducing your travel process costs. You can reduce the instances involved in planning and booking trips, simplify the process itself, and automatically apply your travel policies. It also improves the transparency of costs and of the areas/employees for which they were incurred.
Travel Planning provides an important strategic advantage for the role of the travel manager in your company. The business volume statistics and reporting tools in Travel Planning deliver concrete arguments for rate negotiations with service providers. Managers are relieved of routine tasks and can concentrate on strategic issues such as system and quality management and the optimization of internal processes.
Travel Planning also gives employees more responsibility. The functions are not only intended for experts who use the system on a daily basis to book travel services, they are designed particularly to assist occasional users. Such occasional users could be travelers themselves or secretaries who organize trips for groups of travelers.
Viewed 17471 times by 4437 viewers
The differences between CK11N and CK40N Transaction
The differences between SAP Transaction: CK11N and CK40N. Normally, There is nothing like which SAP transaction is better. They are entirely used for difference purposes.
CK11N :
CK11N transaction is used to calculate the standard cost estimate of the product, for a individual material. The system considers the BOM structure and valuation strategy and control mention in the costing variant and calculates the standard cost of the material. Cost estimate is run or the standard cost is calculated monthly, quarterly etc. and all the analasys of actual production is based against this standard estimate.
You can use this to create the cost estimate for any variant to be used but this will only create a cost estimate. Subsequently you will have to mark and release these estiamtes in CK24 to update in the material master so that you can use the same as the planned price for the materials.
Viewed 19742 times by 5287 viewers
Receivable Management – SAP Process
To access the customer account statement, SAP AR Module has provided FBL5N transaction or Customer display line items for the users. In side this SAP transation, there are much information for users to review or analysis the customer moving transaction for corrective or preventative action.
Customer movement analysis
To understand well the customer moving transactions in the account statement in SAP account receivable system, user may need to understand below customer related transactions, it document types and some necessary components in SAP system as following:
Viewed 21252 times by 5316 viewers
Posting and Clearing Process of Electronic Account Statement
The process involved in the automatic posting of the data from the electronic bank statement in the SAP system.
Information in the Electronic Account Statement
The electronic account statement contains the following information:
- General information on the house bank (bank number and account number, account currency, statement number, and statement date)
- List of individual business transactions that were posted to the account (line items)
Process Flow of Electronic Account Statement
Viewed 21087 times by 5064 viewers
Posting Rules Term (SAP FI-BL)
Posting rules are represented in the system by a non-bank-specific code (for example, TH01: Incoming Payments).
The reason why you require an internal code that is related to the posting rule in order to configure the electronic account statement and why each posting rule not directly linked to an external transaction is…
Banks have many different transactions, several of which may require just a single posting in your accounts.
Example:
Transaction code TH01: Bank Incoming Payments
Transaction code TH02: Interest Received
Viewed 22155 times by 4828 viewers
Join SAP Community:
mySAP ERP | SAP Business | SAP Tutorial | SAP Help
SAP Production Planning Powered By:
