How To Implement Flexible Account in Custom Routine (Case Study)

Purpose of Document

This document explains as-is routine which deals with Flexible Account (or Flex Account).

Business Requirement:

We are using EnterpriseOne with Oracle Transportation Management (OTM) and there is no feature to create accruals for the freight cost. We had to extract data from OTM into custom tables and create the G/L entries and liability records. We needed flex accounting to work but could not figure out the proper business functions and what data to pass; so we hard coded the accounting.
The current situation is that we had to create an other module to handle customs entries and also generate G/L entries and liabilities. The accounting for brokerage and duties also will need flex accounting. This is why we need to know how to implement the routine.
We are using DMAAI's in the 9100 series after getting confirmation from Oracle that the 9100 series would not be used in the future.
In the end, for any company customizing within the distribution system, there might be special needs not available in JDE that flex accounting would be needed like we needed to. Documentation would be welcomed.

Disclaimer:

This document contains some contents which is beyond the support scope of Oracle's JD Edwards EnterpriseOne application release support. Go through full cycle test before you put this raw code not to disturb any standard application logic.

The simplified routine here is adopted from the existing routine of XT4111Z1 which flex account either for MCU or for SUB.The AAI Number, Document Type, Company, G/L Category Code are variables, which you can choose to meet your business requirement. You can use this document to have better understanding on how standard EnterpriseOne applications flex account - if possible, refer to the exiting document which explains setup and examples,

• <Document 756543.1> E1: 42: Flexible Accounting for Distribution (R42800/P4112/P4113/P4114/P4312/P4314/P43291/P40296)
• <Document 786376.1> E1: 43: Flex Accounting in Procurement
• <Document 1449111.1> E1: 31A: Flexible Accounting for Manufacturing (R30835/R31802A/R31804/RF31200/RF31210)

Note that Flexible Account is working for hard-code list of applications as below,

• Inventory: XT4111Z1 (this is representation of inventory transaction P4112, P4113, P4114, P4116, R41413 which may interface with G/L)
• Manufacturing: R30835,R31802A,R31804
• Procurement: P4312,P4314
• Sales: B4200520,R42800
• Asset Management: R12104,R12108,R12845,R12855
• Transportation: R4981

Object Affected:

• New objects:
- 2 Data Structure to handle Edit Line (which validates a record and get flex account before it calls F0911FSEditLine)
- Two BSFN to handle both validation and creation on cache and commit cache to database
- One interactive or batch application to call above BSFN
• Change object
- BuildFlexibleAccountwithCache is to include the custom application/function

Setup:

(For this case study, the object ID used is 'N55FLEX0'. You can define your own object if needed)

1. P1691 (Cost Object Rule Setup Method), add entry for N55FLEX0 with Method 'A - AAI Number method'

2. P16902 (Enabled Functionality by Application) which enable you to list a number of tables which you want to flex

: So function N55FLEX0 can make use of columns from the tables F0006, F0101, F4101, and F4102 (custom table can be added here)

3. P4095 (DMAAI), specify Object Account (repeat this in case you want to flex both Debit and Credit lines)

: For this example, custom DMAAI 9122 (credit line) and 9124 (debit line) are to be used. You must have this one because flexible accounting is part of DMAAI routine

4. P40296 (Flex Rule Definition) - Example,

: So subsidiary of the object account is coming from F4102.BUYR

5. P0901 (Account Master): Make it sure the account you want to flex is defined/added

6. Reset database Cache - Tables F4095, F4096, and F0901 belong to Database Cache (or, a member of P98613)

User Interface:

For this example, one dummy interactive application is created. The data for this add-on application can be added dynamically based on the business requirement. Actual parameters are specified below, which make use of GC or FC variable depending on the level of detail.

Simplified routine:

For this example, one dummy interactive application is created,

BatchReviseOnExit

Business Functions:

For this example, one dummy interactive application is created,

• Business Function : CustomFlexAccountAndCallF0911FSEditLine (N55FLEX0, Custom FlexAccount And Call F0911FSEditLine)
• Purpose: This wrapper function is to Flexible Account and call F0911FSEditLine to create cache for G/L
• Parameter:
• Data Structure: D55FLEX01 - Custom – Flex

• Default routine:
• Others:

• Business Function : CustomFlexEndDoc (N55FLEX0, Custom Flex End Doc)
• Purpose: This wrapper function is to commit cache created through Edit Line and clean up cache used.
• Parameter:
• Data Structure: D55FLEX02 - Custom - Flex End Doc

• Detail routine:
• Others:

---------------------------------- Below are called by the wrapper functions above --------------------------------------------------

• Business Function : FSOpenBatch (B0000042, F0011 Open Batch)
• Purpose: when a certain transactions interfaces with financial module, it is required to write batch header. Additionally this routine isolate a certain transactions to be handled by other process/program.
• Parameter:
• Data Structure: D0000042A - Functional Server- Housekeeping/Open Batch module

• Detail routine:
• Others:

• Business Function : F0911FSBeginDoc (B0900049, F0911 Begin Document)
• Purpose: This Journal Entry Master Business Function to initialize cache, validate header data and create cache for header
• Parameter:
• Data Structure: D0900049A - F0911 - FS Begin Doc

• Detail routine: Map BF mnJobnumberA = VA evt_JobnumberA
• Other considerations:

• Business Function : CacheProcessFlexInventoryAcctng (B4101090, Cache, Process Flex Inventory Accounting)
• Purpose: In this routine, this function is to be called many times depending on cActionCode, which is same with how it deals with cache for Flexible Account
• Parameter:
• Data Structure: D4101090 - Cache, Process Flex Inventory Accounting

• Detail routine:
• Other considerations:

• Business Function : RetrieveDistAAIwF4095Cache (B4000351, Retrieve Dist AAI w F4095 Cache)
• Purpose: This function is to read data (or it's database cache). Note that flexible accounting is to be built based on F4095 so the value you have defined can affect the outcome. For this example, this function is to be called twice likewise we call F0911FSEditLine twice one for Credit Line and the other for Debit Line
• Parameter:
• Data Structure: D4000351 - Retrieve Distribution AAI w/ F4095 Cache

• Detail routine: For this case study, how to map flex account is not reviewed because the flex account is to be built based on this function.
• Other considerations:

• Business Function : F0911FSEditLine (B0900049, F0911 Edit Line)
• Purpose: This master business function validate, default and create cache for GL detail based on the account number returned by above function RetrieveDistAAIwF4095Cache. This function need calling with extra care because it creates F0911 - review your business requirement before implement this.
• Parameter:
• Data Structure: D0900049B - F0911 - FS Edit Line

• Detail routine: Note that for this example, mapping is done with parameters. In case you want to write additional columns to override, you may map it. For this example, repeat same for the offset account.
• Other considerations:

------------------------------ Below is callilng End Doc routine --------------------------------------

• Business Function : X0010GetNextNumber (X0010, X0010 - Get Next Number)
• Purpose: This function is to get F0911.DOC based on given parameters above. End Doc routine increases next number not to waste NN. This is generic function to read either F0002 or F00021. For this case study, szSystemCode and mnNextNumberingIndexNo are sufficient - so below routine is to demonstrate in case you want to have a custom document type (to differentiate it with standard routine).
• Parameter:
• Data Structure: D0000065 - Get Next Number

• Detail Routine: For this example, which is to get IA next number. But you can use any combination of number as long as it is uniquei for the document type you are working on.
• Considerations:

• Business Function : F0911FSGetNextDocNumber (B0900049, F0911 Get Next Document Number)
• Purpose: This function is to update cache created in Begin Doc and Edit Line. So it is important to call this function prior to your calling End Doc.
• Parameter:
• Data Structure: D0900049J - F0911 - FS GetNextDocNumber

• Default routine:
• Other considerations:

• Business Function : F0911FSEndDoc (B0900049, F0911 End Document)
• Purpose: This MBF commits cache created through BeginDoc and Edit Line
• Parameter:
• Data Structure: D0900049D - F0911 - FS End Doc

• Detail Routines:
• Other Considerations:

• Business Function : BatchReviseOnExit (B0000008, F0011 Update on Exit)
• Purpose: This function is to set the batch status to be ready for post (because batch control is off)
• Parameter:
• Data Structure: D0000008 - Batch - Revise On Exit

• Detail Routine:
• Other considerations:

• Business Function : RetrieveF4095Cache (B4000352, Retrieve F4095 Cache)
• Purpose:
• Parameter:
• Data Structure: D4000352 - Retrieve F4095 Cache

• Detail Routine:
• Other considerations:

• Business Function : RetrieveF4096Cache (B4000341, Retrieve F4096 Cache)
• Purpose:
• Parameter:
• Data Structure: D4000341 - Retrieve F4096 Cache

• Detail Routine
• Other considerations:

Hard Coded Application

The Below standard function need updating – all application IDs are hard-coded here.

BuildFlexibleAccountwithCache (N4002371, Build Flexible Account with Cache)
1. Go to OMW (Object Management Workbench)
2. Look for the object N4002371
3. Check out N4002371
4. Go to Named Event Rule design
5. Look for the model function or application you used for this routine
6. Add the application or function ID

Example:

If VA evt_cF4096FetchSuccess_EV01 is equal to "1"
....
Else
If BF szApplicationID is equal to "B03B0025,B03B0067"
...
Else
...
If BF szApplicationID is equal to "N55FLEX0,XT4111Z1"
Cache, Process Flex Inventory Accounting [(CacheProcessFlexInventoryAcctng, B4101090)]
...
End If

The Detail Routines for Flexible Accounting

This section is to explain how you can flex a certain table and columns either for MCU or SUB.

Refer to <Document 1353763.1> - E1: 42: How to Debug Flex Accounting issue in Sales Update.

<Internal_Only> please help me to publish this document - this will be remained internal</Internal_Only>