Customer Master FI SD Integration
Picture the scenario: Due to Sarbanes-Oxly or some other reason the FI part of the customer master is created by the Finance team. After which the SD part of the customer master is created by the Sales team. It is possible that the two teams have failed to communicate to eath other and customer master records can be sitting in your system as incomplete.
To report on these you can use the transaction OV50. This will show you the sales area created customer master records for which there are missing company code views, or visa versa. (A great little utility.)
Execute a Function Module without using SE37
A number of companies restrict the execution of function modules in quality, pre-prod and prod environments, for good reason. Therefore you may find you do not have access to the transaction code SE37. Generally experienced developers may however have access to SE38.
So how do you execute or test a function module in a system/client but wish to get around the authorization issue? Simply use SE38 with program RSFUNCTIONBUILDER.
TIP – You can sometimes use the same technique by using SE93 with the problem transaction and using the program name however do not expect to be able to bypass all authorizations.
Currency and Decimal Places in SAP
The number of decimal places varies for currencies. Currencies which do not have two decimal places must be defined in SAP in table TCURX (decimal places for currency codes).
You can maintain this table in the IMG as follows: SAP Customizing Implementation Guide–>SAP NetWeaver–>General Settings–>Currencies–>Set Decimal Places for Currencies. (Transaction code Oy04)
Never delete a currency or change the decimal place value of a currency in SAP.
Some common Customizing settings for table TCURX:
ISO Currency Decimal places
Code
————————————————————————
ADP Andoran Peseta 0
AFA Afghani Afghani 0
BEF Belgian franc 0
BHD Bahraini dinar 3
BIF Burundi franc 0
BYB Belorussian rubel (old) 0
BYR Belorussian rubel (new) 0
CLP Chilean peso 0
COP Columbian peso 0
DEM3 (Internal) German Mark (3 Dec.) 3
DJF Djibouti franc 0
ECS Ecuadorian sucre 0
ESP Spanish peseta 0
GNF Guinea franc 0
GRD Greek drachma 0
HUF Hungarian forint 0
IDR Indonesian rupiah 0
IQD Iraqui dinar 3
ITL Italian lira 0
JOD Jordan dinar 3
JPY Japanese yen 0
KMF Comoros franc 0
KRW South Korean won 0
KWD Kuwaiti dinar 3
LAK Laos new kip 0
LUF Luxembourg franc 0
LYD Libyan dinar 3
MGF Madagascan franc 0
MZM Mozambique metical 0
OMR Omani rial 3
PTE Portugese escudo 0
PYG Paraguay guarani 0
ROL Roumanian Lei 0
RWF Rwanda franc 0
TJR Tadzhikistani rubel 0
TMM Turkmenistani manat 0
TND Tunesian dinar 3
TPE Timor escudo 0
TRL Turkish lira 0
TWD New Taiwan dollar 0
UGX Uganda shilling 0
USDN (Internal) US Dollar (5 dec.pl.) 5
VND Vietnamese dong 0
VUV Vanuata vatu 0
XAF CFA Franc BEAC 0
XOF CFA Franc BCEAO 0
XPF CFP Franc 0
The contents of this table is only delivered with new installations of SAP and never upgraded.
For upgrade installations, new or changed contents of Table TCURX are not delivered.
Currency codes and decimal places for currency codes are defined in ISO standard 4217. For the specification of decimal places for currency codes, SAP uses this ISO standard.
Functional Domain Tables
Here are a list of tables which you may find useful related to their domain.
SM12 – Lock Entries Tips
If you check SM12 you may find some lock entries – this is not a problem. Locked entries are required in standard SAP processing. In most instances the entry will remain in SM12 for a few seconds milliseconds, however they could remain in SM12 for a lot longer depending on the logical unit of work.
Factors which can impact the entry in SM12:
- Sizing and performance of the enqueue server.
- Sizing and performance of the application server/number of available processing sessions. (indirectly related)
- Program logic being executed on the application server.
What you may not know is that there is a hidden menu path for SM12 analysis. To activate this menu path you can do the following:
Run SM12, then enter OK code “test”. You will now see the top menu path has included a new Menu Option labelled “Error Handling”.
This menu option has many parameters and test functions which you can use to analyse the enqueue and dequeue processes.
If you require advice on how to use this new functionality you can refer to OSS note 5424 which is the SM12 FAQ! Success!
Work Faster in the IMG – Restrict Selections
It is possible you may be in a configuration screen which either has too many entries from which you wish to select to analyse, or you may need to select specific entries based upon values which are not part of the key of the table/configuration screen.
You could navigate to the table and do checks in SE16N or SQVI etc. Or…… the next time you are in a configuration node of the IMG, try the following tip:………
Select the following from the Top Menu Navigation Bar: Selection–>By Contents
Then select the Fields you require to filter the configuration entries.
Command Line “OK-Codes”
Direct call of transactions, session handling:
/nxxxx
- This terminates the current transaction, and call transaction “xxxx”, for example, “sa38″ for reporting.
/n
- This terminates the transaction. This generally corresponds to going back with F15.
/nend
- This terminates all separate sessions and logs off (corresponds to “System -> Log off”).
/nex
- This terminates all separate sessions and logs off immediately (without any warning).
/oxxxx
- This opens a new session and starts transaction xxxx in this session.
/o
- This lists existing sessions and allows deletion or opening of a new session.
/i
- This terminates the current session (corresponds to “System -> End session”).
/i1 , /i2 ,…
- This terminates the session with the specified number.
.xyzw
- “Fast path”: “xyzw” refers to the underlined letters in the menus. This type of navigation is uncommon and is provided more for emergencies (such as a defective mouse).
Background input:
The following commands can be entered in correction mode (“Process in foreground” or “Display errors only”) when processing a background input session: Read more 
Number Range Buffering
Basic Introduction to NRIV
The document number is assigned in chronologically ascending order based on the table NRIV. For this, the table NRIV is locked until the application (LUW) is terminated by either a COMMIT WORK or ROLLBACK (OSS Note 639754). Another application cannot take a document number during this time. Read more
Where does the system determine the Accounting Doc Type?
The Accounting document type is determined in various ways, according to type of transaction, for example the default can be configured in SAP Customizing Implementation Guide–>Financial Accounting–>Accounts Receivable and Accounts Payable–>Business Transactions–>Outgoing Invoices/Credit Memos–>Carry Out and Check Document Settings–>Define Default Values
However in the case where you have a sales billing document and you would like to default a specific accounting document type you should Read more
Transaction Codes – FI
F-01 Enter Sample Document
F-02 Enter G/L Account Posting
F-03 Clear G/L Account
F-04 Post with Clearing
F-05 Post Foreign Currency Valuation
F-06 Post Incoming Payments Read more
Revenue Recognition
1. Is it possible to use a customized document type for the revenue recognition in FI?
2. Why is a revenue recognition not possible, and why is an entry made in the incompleteness log of the order or contract?
3. How can I use the revenue distribution, and what is the purpose of the revenue distribution?
4. When is an update of the revenue recognition data required, and how do I execute this update?
5. When are the sales costs transferred to CO-PA during the revenue recognition process?
6. Why are not all fields filled in the CO document for the revenue recognition documents that are also filled during the billing document transfer?
7. Why is the account for non-billed receivables, and not the account for deferred revenues, posted in the case of revenue recognition-relevant items in the credit memo?
8. Why is monitoring of the revenue recognition data required, and how do I monitor the data? Read more
Revenue Recognition Cancellation
Why does transaction VF46 (Revenue Recognition: Cancellation) not cancel the revenue recognition posting?
The revenue recognition cancellation (transaction VF46) is not a real cancellation in the sense of a reverse posting, but a posting to a prior period. This is based on the balances in the accounts when the cancellation is created.
Plants Abroad – Great OSS notes
Here are the OSS notes you need to know of when implementing Plants abroad in SAP: Read more
Material Account Assignment
Q – When I look at a material movement accounting document, how does one see an example of the determination used in the account assignment?
A – Use config transaction OMWB, select the chart of accounts/or press cancel. Then Select the Simulation button. Enter plant + Material + Movement type to see the account assignment.
