How to Populate a certain columns in F4111 (Item Ledger) through P4116

Purpose of Document

Title: How to populate addition User Reserved Columns into F4111 table through P4116 or other inventory transaction.

Abstract: This document explains how a certain unused columns can be added through Inventory Transaction (P4112, P4113, P4114 and P4116). Same routine can be applied in any routine which calls the Inventory Transaction Master Business Function XT4111Z1.

Caution: This document may contain information, software, products or services which are not supported by Oracle Support Services and are being provided ‘as is’ without warranty. Please refer to the following site for My Oracle Support Terms of Use: https://support.oracle.com/CSP/ui/TermsOfUse.html

Table of Contents

• Introduction
• User Interface
• Action Plan
• Possible Implementation
• Objects Affected

Introduction

Before implementing, try to understand the logic on how the system handles Inventory Transaction. Currently a table F41UI001 is used to store inventory transaction as temporary repository.

Currently P4116 (Item Reclassifications) handles data as below,

1. Call XT4116Z1 - F4116FSEditLine (F4116 FS Edit Line) to hand over grid columns to internal BSFNs to be called
2. Then F4116FSEditLine calls XT4111Z1 – F4111EditLine (F4111 Edit Line) to validate/default/create cache of F41UI001
3. In clicking OK button F4116FSEndDoc routine is calling F4111EndDocument (F4111 End Document) routines to commit inventory cache to F4111 – Cardex (Inventory Transaction File)

Note: For this example, XT4116Z1 is NER code whereas other inventory transaction master business function XT4112Z1, XT4114Z1, XT4114Z1 are written in C Codes. However the way you can implement is same.

For this example, we may modify below objects to accommodate this request,

• Business View: V4111F because DOCO, DCTO and KCOO are not a member of business view V4111F which is associated with P4116 (Inventory Reclassification)
• Data Structure: DXT4116Z1C because three columns listed above is not a member of data structure
• XT4116Z1 (NER): In calling XT4111Z1 (F4111EditLine) which does not handle listed columns
• Application: P4116 to assign GC value to XT4116Z1 (Edit Line) routine

Back to Top

User Interface

This will describe simple and standard functionality based on Adding a new grid rows.

• 1.     Launch ‘Item Reclassifications’ P4116 – W4116W [Item Reclassifications]
• 2.     In Exiting Grid Row hands over User Input value into Edit Line routine and (in Update Mode) show value from F4111 into grid

 

Action Plan

• Verify existing logic in creation of F4111
• Study the NER Code of XT4116Z1 (this is named event rule code)
• Determine how User input value has to be written to cache (Work File), Cache Name and detailed routine.

Note that this routine can be applied any type of inventory transaction so long as Cardex file is written through XT4111Z1 master business function routine. However we discourage you from your modification from standard routine because additional columns and/or additional routine may be in place in the future which can be conflict with the example written here.

1. Add User Reserved Columns in Business View F4111F
2. Show columns in Grid of W4116B
3. In calling Edit Line in W4116B assign newly added columns in step 2
4. In calling X4111Z1 – F4111EditLine assign the value assigned in step 3
5. Test change made

Possible Implementation

1. Business View: V4111F because DOCO, DCTO and KCOO are not a member of business view V4111F which is associated with P4116 (Inventory Reclassification)

Alternatively you may handle data dictionary items in P4116 to minimize modification. For this case, data from F4111 has to be fetched/updated as designed

1. Go to OMW
2. Check out V4111F
3. Go to Design
4. Select columns DOCO (DocumentOrderInvoiceE), DCTO (Order Type) and KCOO (CompanyKeyOrderNo)





IMPORTANT: this is change of data structure so any change has to be done with extra care.

1. Save changes
2. Create a type definition to enforce system to understand the change. If needed, delete glbltbl.xdb and ddb from spec directory you are working on (which create bv4111f.h in include folder)
3. Check in
1. Data Structure: DXT4116Z1C (F4116 FS Edit Line) because three columns listed above is not a member of data structure
1. Check out DXT4116Z1C through OMW
2. Go to Data Structure Design





1. Create a type definition



1. Check in
1. XT4116Z1 (NER): In calling XT4111Z1 (F4111EditLine) which does not handle listed columns
1. Check out XT41116Z1
2. Go to “Start Business Function Design”



1. (Form Exit) > Edit







1. Compile it by clicking “build business function”
1. Application: P4116 to assign GC value to XT4116Z1 (Edit Line) routine
1. Check out P4116
2. Go to Form Design Aid
3. Add 3 Grid Control Columns into FC Grid





1. Go to the event “Row Exit & Changed – Asynch” event and assign GC controls in calling F4116 FS Edit Line









Objects Affected

• Business View V4111F
• NER XT4116Z1
• P4116

Back to Top

E1: FDA: Object Modification Recommendations: Interactive Applications (Doc ID 626586.1) 

E1: FDA: Object Modification Recommendations: Event Rules (Doc ID 626585.1) 

E1: TDA: Object Modification Recommendations: Business Views (Doc ID 626582.1) 

Back to Top