Short dump in t-code CJ30 while updating budget

Symptom
When a user attempts to modify budget allocations to a project from transaction code CJ30, the following ABAP runtime error (short dump) is resulted.

Runtime Errors : MESSAGE_TYPE_X
System error in : OBP_GE
Report : LBPFCF81
Routine : BUDGET_FILL_TBPJA_XX

screenshots:

Cause*:

The above condition may result when a configuration change is made to the project profile using t-code OPS91

Solution:
1. Execute transaction CJBW to deactivate availability control for the concerned project
2. Reconstruct availability control using transaction CJBN
3. Maintain budget in CJ30.

* This is one of the causes, there can be various other reasons for such dump.

Add document header text (BKPF-BKTXT) to dynamic selection in FB03,FBL3N,FAGLL03

Requirement
Doc. Header Text to be added in the dynamic selection in FB03, FAGLL03 etc.

Solution
Refer to the reply from Jeccas_DJ on the following SDN thread
https://forums.sdn.sap.com/thread.jspa?threadID=357594&tstart=0

Incorrect occurances of record type 31 in BTL91 format

What is BTL91 format ?
BTL91 is foreign bank transfer format used in Netherlands
BTL91 is available is SAP DME as tree BTL91 of type PAYM, for use with Payment Medium Workbench (PMW) and other transactions.

What is record type 31?
Each file generated for BTL91 format contains footer records starting with constant '31'.
The record consists of currency wise summary of the detailed transfer records.
for example:
If the file contains 3 transactions for currency USD, 2 transactions for currency GBP and 1 transaction for currency INR ( in a single batch)
The BTL91 file generated for this example should contain three records of type 31, one each for USD,GBP and INR with the total transaction amounts for each currency.

Issue:
File generated from SAP program SAPFPAYM (T-code: FBPM) carries multiple record type 31 for same currency
For example: 2 records with USD, 2 records with GBP and 1 with INR for the example used above

Solution:
The issue of multiple records type 31 is caused due to a program error while generating the DME/PMW file
It can be rectified by the applying SAP Note 1136370 - DMEE PAYM: REGUH-SRTF1 is wrongly filled
Even after implementation of the above note, the problem may persist for the payment runs for which DME file has already been generated incorrectly. This is due to the fact that sort data for such payment runs is already stored in the system. To rectify such cases user may execute the program RFPAYM_RESET for these payment run to resent the payment medium information.

Information: Document splitting with Dummy Profit Center

Observation:
When an accounting document is posted with a dummy profit center, the dummy profit center is replaced with the profit center derived from the document splitting rules in the general ledger view of the document, while the profit center accounting (PCA) document is posted to the dummy profit center only. The entry view of the financial accounting document also displays the dummy profit center, however the general ledger view displays the derived profit center.

In the above scenario if the zero balance setting is maintained for the field profit center, No zero balance offsetting posting is made with respect to the amount posted to the dummy profit center.
For example:
Entry view for a Posting with Dummy profit center

Entry view for a Posting with Dummy profit center
Co Code	Item	PK	Account	Account Description			Amount	Currency	Profit Center
XX01	1	40	6700000	GL account			50	INR	XXPRFCNTR01
XX01	2	50	6700000	GL account			-50.00	INR	XXDUMMY
General Ledger (GL) View / Dummy profit center is replaced with the derived profit center
Co Code	Item	PK	Account	Account Description			Amount	Currency	Profit Center
XX01	1	40	6700000	GL account			50.00	INR	XXPRFCNTR01
XX01	2	50	6700000	GL account			-50.00	INR	XXPRFCNTR01
Entry view for a Posting with a non-dummy profit center
Co Code	Item	PK	Account	Account Description			Amount	Currency	Profit Center
XX01	1	50	6700000	GL account			-40	INR	XXPRFCNTR01
XX01	2	40	6700000	GL account			40	INR	XXPRFCNTR02
General Ledger (GL) View / Zero balance clearing postings are made
Co Code	Item	PK	Account	Account Description			Amount	Currency	Profit Center
XX01	1	50	6700000	GL account			-40	INR	XXPRFCNTR01
XX01	2	40	6700000	GL account			40	INR	XXPRFCNTR02
XX01		50	2050000	Zero Balance Clearing account			40	INR	XXPRFCNTR02
XX01		40	2050000	Zero Balance Clearing account			-40	INR	XXPRFCNTR01

The above scenario occurs if the following preconditions are satisfied
1. New GL is active
2. Classic profit center accounting is active
3. Profit center update scenario is assigned to the concerned ledger
4. Profit center is a maintained as a characteristic for document splitting
5. Zero balance setting is maintained for Profit Center characteristic in document splitting

More information on this behavior is available in the following SAP Notes
0000826357 - Profit Center Accounting and New General Ledger in SAP ERP
0000871277 - IMG documentation, G/L acctg (FI-GL new), document splitting
0000891144 - New GL/Document splitting: Risks w/ subsequent changes

Cost Center not updated in General Ledger view, New GL tables

Issue
A Financial Accounting document has been posted in the system with multiple CO account assignment objects, and some Controlling account assignment objects of the entry view are not updated in general ledger view.
For example: A FI document is posted with a WBS element and a Cost Center, and the cost center is displayed in the entry view of the document (FB03) but not in general ledger view. The cost center is also not updated in table FAGLFLEXA and hence does not appear in GL line item display transaction FAGLL03 as well.
Even when New GL is active and Cost Center Update scenario (FIN_CCA) is assigned to the concerned ledger

Solution
This behavior occurs if the CO account assignment is statistical and not actual (real).
In the above example, If the WBS element involved in real, the posting to Cost Center would only be statistical and thus it would not be updated in New GL tables. However, if the WBS element involved is statistical, the posting to Cost Center would be real (actual) and it would be updated in general ledger view and New GL tables.

The following SAP Note provides details of this system behavior
Note 964686 - Transfer of statistical postings in CO to FI

References
Thanks to Radha and Sanil for answering this query on SAP forums at the following thread
https://forums.sdn.sap.com/thread.jspa?threadID=1305266&tstart=0

Report S_ALR_87012174 displays cleared items

Issue
The report S_ALR_87012174 - List of Customer Open Items , displays cleared items also.
(Program Name: RFDOPO10)

Solution
Implement SAP Note 1164663 - RFDOPO10: system incorrectly displays cleared items

Trivia: Basic criteria for selection of Leading Ledger

Only the Leading Ledger in FI New GL posts to CO. Hence the basic premise of selecting the Leading Ledger is to identify whether the Local GAAP or Global GAAP is in synchronization with the Controlling requirements.

Trivia: Access NewGL IMG menu without activation of New GL

The (spro) configuration menu for Financial Accounting (New) / New General Ledger (New GL) can be accessed without activation of New General Ledger using transaction code FAGL_FLEXGL_IMG.

New GL can be run parallel to classic GL

Incorrect Book Value in Asset Explorer and Asset History Sheet

Module: FI-AA (Financial Accounting - Asset Accounting)

Issue: Incorrect book value in Asset Explorer and Asset History Sheet
Asset explorer: shows incorrect Fiscal year-end value
Retirement transaction of 594173,13 is not included in change

In the asset history sheet as on 31-12-2008 transfer using Transaction Type 340 is not subtracted from the book value at FY start to calculate the current book value

In the asset history sheet as on 30-11-2008 value of retirement transfer using Transaction Type 340 is subtracted from FY start book value to arrive at the currency book value

Table ANEP(Asset Line items) shows the correct net book value

Table ANLC (Asset Value Fields) displays incorrect values

Solution : Execute t-Code AS02, Open the asset master data and click the menu option Edit > Recalculate Values.

After Recalculation
Asset Explorer (Aw01n) shows the correct year end and change values

Asset history sheet as on 31.12.2008 also stands corrected

Table ANLC is Updated

Trivia: Assignment of Segment to a Profit Center

What is Segment ?
Segments can be used to meet international accounting rules (=> IAS / IFRS / U.S. GAAP) regarding "segment reporting".

Excerpt from IAS 14: … reporting is required for a business or geographical segment when the majority of its revenues stems from sales to external customers and segment revenues account for at least 10% of total internal and external revenues of all segments, segment income accounts for at least 10% of all segment income, or segment assets account for at least 10% of the assets of all segments. A segment can be reported separately even if it does not meet these size requirements. If the segments subject to reporting requirements account for less than 75% of total consolidated revenues or enterprise revenues, then other segments must be reported on separately, irrespective of the 10% limit, until at least this 75% is reached. …

The Business Area or Profit Center objects can be used as alternatives.
The segment is provided in addition because the business area and/or profit center were frequently used for other purposes in the past, to meet other requirements.

Assignment of Segment to a Profit Center
Note: Once a Segment is assigned to a Profit Center, It cannot be changed. Hence one has to be very very careful in assigning a segment to a profit center.

BDC error when processing in Background

What is BDC?
BDC (Batch Data Communication) is an ABAP programming technique, which allows to record and playback SAP user transactions using an ABAP program
More information on BDC can be accessed at the following SDN Wiki link :
https://wiki.sdn.sap.com/wiki/display/ABAP/BDC

Various Modes of BDC execution ?
Once an BDC has been recorded using SHDB it can be run in an ABAP program by using statement CALL TRANSACTION
for example :
CALL TRANSACTION l_c_tcode USING i_bdcdata
UPDATE l_c_update
MODE l_c_mode
MESSAGES INTO i_bdcmsg

More details on the "CALL TRANSACTION" statement are available at the following SAP Help link :http://help.sap.com/abapdocu/en/ABAPCALL_TRANSACTION.htm

BDC Modes
An ABAP program may use one of the following common mode options for the call transaction statement
A - Execution of the transaction with display of each transaction screen
E - Execution in background with display of transaction screen only in the case of an error
N - Execution in background without display of transaction screens

A mode is generally used to run the BDC while the program is in development to test the exeuction of each screen of the transaction under various conditions. while the N mode is generally used for integration or performance test

Issues
Certain messages, like the ones listed below may appear as an information or warning message while a BDC is executed in A mode.
example : Field BSEG-ZTERM. is not an input field

Solution
A consultant should check all the conditions where the ABAP program may try to enter data in a field which may or may not be available for input depending upon inputs in previous screens of the transaction or otherwise.
All such inputs should be avoided or controlled by adding adequate program logic conditions in the ABAP code.
For Example :In transaction F-32, if no residual item is created, the Payment Term field ( BSEG-ZTERM) for the first line item of the FI document would not be available for input. but when a residual item is going to be created, the first line item would contain the residual amount to be posted and its Terms of Payment would be editable (depending upon field status group and document layout settings)Hence the above logic of determining the residual amount needs to added to the program logic