How to Record Zero Balance Adjustment

Purpose of Document

This note is to explain possible way to implement ZBA (Zero Balance Adjustment) through Report Design Aid.

DISCLAIMER
The following is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.

Through this note,

• Understand how Inventory Transaction master business function is working
• How to populate F4111 (Item Ledger) and F0911 (General Ledger)
• How to make system update Average Cost
• Currently Zero Balance Adjustment can be input through P4112 (Inventory Issue) and P4114 (Inventory Adjustment)

Business Scenario:
Possibly, enter purchase order with quantity of 504,000 GM at purchase unit price of $1438.0531, which computes extended price of 724,778.76 (= $1438.0531 x 504000 / 1000) where Transaction UOM is equal to GM (same as primary) whereas Purchasing UOM is equal to KG
Through P4116 (Inventory Reclassification), transfer good received above to another branch plant with quantity 504,000 at $1.4381 (=724,802.40), which cause outstanding amount of $23.64 where quantity is zero.
[As - Is Transaction in F4111 - Cardex]

: Outstanding balance 23.64 contribute average cost change


Considerations:

• Add custom report into UDC 40/AV - Average Cost Calculation (Refer to <Document 625564.1> E1: 41: Weighted Average Cost (P4105/R41811/P4205/P4312/P4114/P4112) to include Zero Balance Adjustment in computing Average Cost
• Item, Branch/Plant, Location, Lot can be have one set of data. In case inventory cost level is different, level break can take place at different level
• ZBA computation has to take place regular basis when you need to have cost analysis for example
• Need to handle only when quantity is zero but amount is not zero
• It is able to deal with both Positive and Negative amounts as it is handled from P4112 for negative and P4114 for positive
• Write F4111/F0911 with descriptive explanation/description
• It is not required to validate/default values since it gets data from valid transaction

Related transaction file master business function:
X4114Z1 handled transaction as below,

Relationships:

: Review relationship among master business functions

After transaction:

• F4111 - Cardex

• F0911 - General Ledger

Detail Implementation:
This is just an example, so try to understand this as how EnterpriseOne handled transactional cache. If possible, capture callobject kernel log (namely jdedebug.log) and analyze it
1. Go to OMW (Object Management Workbench)
2. Add a report
3. Create section using a business view (for instance, V4111B - Item Ledger Detail)
4. Set Sequence by LITM, MCU, LOCN and LOTN and set Level Break for same sequence. This is to summarize quantity (F4111.TRQT) and amount (F4111.PAID) at level break footer
5. Create Level Break Footer and Aggregate for columns F4111.TRQT (QuantityTransaction) and F4111.PAID (AmtExtendedCost)
6. Define variables to handle among master business functions (for this implemenation below variables are defined) as below,

• rpt_szComputerID_CTID: This can be used across system so call this only once. In creating transaction file cache szComputerID is one element for that along with Job Number
• rpt_mnJobnumberA_JOBS: This variable is job number of inventory transaction. For this transaction at least 2 different job number will be used (one for Inventory and the other for GL - General Ledger
• sec_cBeginDocError_EV01: This is return value from begin doc to determine whether to proceed further or not
• sec_jdDateBatch_DICJ: Through begin doc in getting batch header information this value is to be used. Either assign it manually or let system assign it using system date
• sec_mnJELineNo_JELN: For this example, this is optional because only one entry is to be created per ZBA
• sec_szCompanyKeyOr_KCOO: This is one unit for GL Cache which is to be returned based on Branch/Plant in Begin Doc. Or we can assign F4111.KCO
• sec_szDocumentType_DCT: Depends on the sign of variance (i.e., Negative or Positive) we set this value either 'II - Inventory Issue' or 'IA - Inventory Adjustment'. Or you can define your own document type supposed that DMAAI is set properly
• sec_jdDtGLAndVouch1_DGL: Either assign a specific date or let system determine it using today's date
• sec_jdDateTransa_TRDJ: To recognize actual date transaction is performed
• sec_szExplanation_DL01: Currently this value is not used because Explanation for G/L shall override this value
• sec_cEditLineError_EV02: To get validation result in calling Edit Line (XT41114Z1 sets 1 for ERROR)
• sec_cWriteWorkFile_EV01: For inventory transaction this value is always a space because either Inventory or GL it utilizes cache (not work file)
• sec_mnOrderLineNumber_LNID: This value can be always 1.000 because we deal with a single line of transaction
• sec_szExpla_TREX: This is actual transaction explanation which possibly indicate the source of transaction (descriptive one) do not exceed 30 characters
• sec_mnPrevLine_LNID: This variable is to handle when there is multiple transaction for this example, this value is to be always 1.000
• sec_mnTransactionLineNr_TRNO: Same with above
• sec_cFromTo_FRTO: This is to indicate the diretion of transaction. For example, set F - From for Negative amount and T - To for Positive amount
• sec_mnBatchNumber_ICU: Through begin doc routine let it handle batch header since this transaction is to write Gengeral Ledger
• sec_cBatchStatus_IST: This is to be used internally so get status from begin doc and assign it to edit line and end doc routine
• sec_szUnitOfMeTransact_TRUM: this is actual transaction UOM. In this case primary UOM or smallest UOM will be written. This variable is defined because we handled transaction at level break footer level
• sec_mnJobnumberA_F0911_JOBS: This is job number in creating/consuming GL Cache
• RV 2nd Item Number, RV Business Unit, RV Location and RV Lot/SN: To show PC (Previous columns) because all these routines are written in Level Break Footer Section

*** Continued ... ***
SECTION: On Lot/SN [GROUP SECTION] ()
EVENT: Initialize Section

7. Call B9800181 - GetLocalComputerId as below,
Get Local Computer ID
VA rpt_szComputerID_CTID <- BF szMachineKey *** Now machine ID of client is returned, which is to be used in Edit Line and End Doc routine ***
: Put this event where it gets called only once

EVENT: Do Section

8. Assign Previous Columns to Report Variable to print out (in case you do not need any output this step is not needed)
RV 2nd Item Number = PC 2nd Item Number (F4111)(LITM)
RV Business Unit = PC Business Unit (F4111)(MCU)
RV Location = PC Location (F4111)(LOCN)
RV Lot/SN = PC Lot/Serial Number (F4111)(LOTN)

9. Compute Amount to Adjust by multiplying (-1) to zero Total Amount
RV mnAmtToAdj = [RV Summary_Extended Cost/Price]*-1

10. (Optional) call B4100730 - AccumulateItemQuantities (F41021 Get Item Quantities) per level you want to segregate. Now you can compare on hand quantity from F41021 (Item Location File) with Total F4111.TRQT

11. Step 5 has aggregated quantity and amount so now we can use it to determine whether to proceed transaction or not. Handle data only when total quantity is zero BUT total amount is not zero

If RV Transaction Quantity is equal to <Zero> And RV Summary_Extended Cost/Price is not equal to <Zero>

12. Assign document depends on variance returned (e.g., Negative then need to write positive amount which is equivalent to Inventory adjustment)

If RV Summary_Extended Cost/Price is greater than <Zero>
VA sec_szDocumentType_DCT = "II"
Else
VA sec_szDocumentType_DCT = "IA"
End If

13. Set Explanation for Inventory Transaction (i.e., how to F4111.TREX gets written). For this example, this value is to be overriden by Explanation Code for GL

VA sec_szExplanation_DL01 = "Zero Blance Adjustment - Custom"

14. Call XT4114Z1 - F4114BeginDocument (F4114 Begin Document)
F4114 Begin Document
: Below table is to show how the value is assigned/returned based on data structure DXT4114Z1B : F4114 Begin Document - Functional Server

15. Check whether Begin Doc returns error (then exit from routine) else continue to call Edit Line which validates/creates cache for Inventory (F41UI001) and GL (I09UI002, I09UI003)

If VA sec_cBeginDocError_EV01 is not equal to "1"

16. Set flag for cWriteWorkFile, TREX, TRNO, FRTO and TRUM (explanation in detail parameter)


VA sec_cWriteWorkFile_EV01 = " "
VA sec_szExpla_TREX = "Zero Balance Adjustment - GL"
VA sec_mnTransactionLineNr_TRNO = "1.000"
If RV Summary_Extended Cost/Price is greater than <Zero> *** Positive amount then target amount is negative ***
VA sec_cFromTo_FRTO = "F"
Else
VA sec_cFromTo_FRTO = "T"
End If
VA sec_szUnitOfMeTransact_TRUM = PC Unit of Measure - Transaction (F4111)(TRUM)

17. Call XT4114Z1 - F4114EditLine (F4114 Edit Line). For this example, Edit Line gets called only once. In case you need to create multiple inventory cache you need to check change of company, document type and call Edit Line routine for each rows. Note below are shown only parameters assigned. So reveiw Edit Line routine if needed, you can populate more parameters.

F4114 Edit Line
: Below table shows parameters mapped based on Data Structure: DXT4114Z1C : F4114 Edit Line - Functional Server

18. Continue to commit cache to tables (F4111, F0911 and so on) if Edit Line did not return Error

If VA sec_cEditLineError_EV02 is not equal to "1"

19. Call XT4114Z1 - F4114EndDocument (F4114 End Document) to commit cache created through Edit Line routine

F4114 End Document
: Below table is to show actual parameter mapped based on data structure DXT4114Z1E : F4114 End Document - Functional Server

End If
End If

20. (Optional) call XT4114Z1 - F4114ClearDetailStack (F4114 Clear Detail Stack) based on Job Number returned from Edit Line. In case a certain transation has to be cancelled in a certain routine this function shall delete all caches created

F4114 Clear Detail Stack
: Below table is to show actual parameter mapped through data structure XT4114Z1 Clear Detail Stack - Functional Server

End If

Reference:
<Document 625466.1> E1: 41: Zero Balance Adjustments
<Document 1276239.1> E1: 41: Inventory Transaction MBF XT4111Z1 Clarification
<Document 1265902.1> E1: BSFN: Master Business Function in EnterpriseOne