How to Debug Issue on P38200W (Agreement Selection Window)

Purpose of Document

Goal

This document is a guide to help debug issues from Agreements, which interfaces with various applications. In various applications, the application/form P38200W/W38200WB enables you to select a specific agreement based on an Agreement Cache created through a routine you are working on.

Table of Contents:

Application/from calling P38200W
Related Business Functions
Table/Column Explanation
Example of CallStack

New Order - Add Mode

Create Cache
Read Cache

Exiting Order - Update Mode

Validate Agreement

Data Structure Used in the routine
- D3800050A
- D3800050B
- D3800050C
- D3800050D
- D3800070
Case Study

Application/form which is calling P38200W/W38200WB - [Agreement Selection Window]
: Interactive application listed below can call W38200WB form to enable the user to select the proper Agreement which meets the condition. Refer to <Document 625523.1> E1: 38: Agreement Management (P38010 / P38020 / F38010 / F38011 / F38111).

Only when Agreement Number (DMCT) and Agreement Supplement (DMCS) are not populated, which indicates/enables you to select the agreement from multiple active agreements.

Application Name	Calling Form	Calling Form Description	Others
P415101	W41510B	General Stock Movement	This application is for General Stock Movements (P415101) for bulk items. This application updates Bulk Ledger, Bulk AAIs, Gain/Loss if needed.
P4205	W4205K	Shipment Confirmation	Product can be borrowed from a partner without actually receiving the product into inventory. The partner can ship the product directly to the customer.
P4210	W4210A	Sales Order Detail Revision	Sales Agreement only when Agreement Number and Supplement are not populated.
P4310	W4310A	(Purchase) Order Detail	An agreement to borrow from a business partner.
P49640	W49640B	Confirm Load - Compartments	Transportation Load Confirmation through P4960
P49660	W49660A	Disposition Load	Disposition Load through P4960
P49660	W49660A	Disposition to Multiples	Disposition Load to Multiples through P4960

Agreement Search Related Business Functions:
From the list below, the NER is controlling process and C function handles cache (AgreementCache)

Source ID	Function Name	Usage	Notes
N3800050	F38010AgreementSearch (F38010 Agreement Search) Data Structure: D3800050A	1. Called by F38012 Full Edit Mode (or Edit Line MBF) 2. Its objective is to establish the way it is going to search the agreement information 3. it defines if the search is going to be based on Destination, Source, Source/Destination, or no search is needed. 4. After the Mode is established, the process will call F38012 Search Mode Mode 1 = by Destination Mode 2 = by Source Mode 3 = by Source/Destination Mode 1 = no search
B3800070	F38010AgreementCache (F38010 Agreement Cache) Data Structure: D3800070	This C Business Functions stores/handles cache during a certain transaction with key of szComputerID mnJobNumber mnOrderNumber szOrderType szOrderCompany szOrderSuffix mnLineNumber szAgreementNumber mnAgreementSupplement mnSequenceNumber szAgreementSource szAgreementType In transaction if you do not get any agreement cache, make sure all the key values are correctly populated from related tables (F38012, F38010 and F38011). It is called AgreementCache and cache name B3800070+JobNumber with data structure ID DSD3800070A * This function does not call any other business function or table value so if you want to have correct cache information all the values have to be populated correctly in calling this C Function.	cModeProcessing 1- ADD 2 - GET - Fetch based on the cursors 3 - full key update 4 - get next 5 - Update 6 - delete record based on a partial key with 7 fields 7 - DELETE - ALL 8 - FETCH FULL KEY 9 - Terminate the cache
N3800050	F38012SearchMode (F38010 Search Mode) Data Structure: D3800050B	Search data from F38012 (Product Source/Destination) Master based on cModeProcessing The sequence for checking Agreement Master is, 1. F38012 (Product Source/Destination Master) depends on input cModeProcessing it sets SELECT and returns data from F38012 2. F38010 (Agreement Master) to get information of DL01, DMTC, DMSC, AN8, QEDT, CAND, UPGL, PRAS, CMOO and CNQY based on DMCT and DMCS which are returned by cModeProcessing '4' or 'others = NOT IN ('1', '2', '3') 3. F38011 (Agreement Quantities) to get information of SEQ, AA, UOM, MINQ, MAXQ, UPRC, ASN, MCU and CRCD	cModeProcessing: This parameter determines how to fetch data from F38012 (Product Source/Destination Master) 1 - Select Data based on ITM, DTO, DES and DESY on Index F38012_EXPIRED_DATE (Key2) 2 - Select Data based on ITM, DTO, PSR, PSRY on Index F38012_EXPIRED_DATE (Key2) 3 - Select Data based on ITM, DTO, DES, DESY, PSR, PSRY on Index F38012_EXPIRED_DATE (Key2) 4 - Fetch Single based on DMCT, DMCS, SEQ, PSR, PSRY on Primary Key (It returns the very first row based on primary key) ELSE - Loop by calling F3812.FetchNext to get DMCT, DMCS, ITM, DTO, DES, DESY, SEQ, PSR, PSRY, CNQT, AA, UOM, MINQ, MAXQ, QBAL, QCOM, EFTJ and EXDJ
N3800050	F38010FullEditMode (F38010 Full Edit Mode) Data Structure: D3800050C	This NER can call N3800050 F38010AgreementSearch (F38010 Agreement Search). For example, if you specify the Agreement Number in Grid of Sales Order Entry, this NER gets called by the F4211FSEditLine routine to validate and call B3800070 which handles data through cache	This function gets called during the edit line routine of a certain master business function when agreement number is specified (= Not Blank)
N3800050	F38010DeleteAgreementCache (F38010 Delete Agreement Cache) Data Structure: D3800050D	This NER in return calls B3800070 - F38010AgreementCache (F38010 Agreement Cache) with cModeProcessing '7' to delete all the caches during a certain process

Note:

If needed, capture both JASDEBUG which traces runtime process and JDEDEBUG which traces callobject (business function) flow to verify further. In the log, check cModeProcessing which determines how to fetch data from Agreement Master tables.
Review relationship among F38012, F38010 and F38011. All agreement search is first done based on F38012.

Table/Columns Explanation:
Below table is to show columns requested for a specific table.

Table	Column	Description	Note	Usage
F38012	DMCT*	ContractNumberDistributi	Agreement Number - Distribution A unique number your company assigns to identify a particular agreement. You might want to assign some significance to the agreement number (for example, an agreement type code, location, year, and so forth). An agreement might have multiple supplements to record addendum or changes, for example.	Used for Unique Agreement Information along with DMCS below
	DMCS*	ContractSupplementDistri	Agreement Supplement - Distribution The supplement number records any changes or addendum to agreements that occur over time or by item. It can also indicate individual agreements that are tied to a master agreement. The system allows up to 999 different supplements per base agreement number.
	ITM	IdentifierShortItem	Item Number - Short	Item Number entered during Sales or Purchase Order
	DTO	DueTo	Due To, UDC (38/DT) - Due To A code that identifies which partner is due to receive the listed item. Valid values are: C Company - Your company expects to receive product from the partner. P Partner - Your partner expects to receive product from your company.	Example of data: C - for Purchase P - for Sales
	DES	Destination	Destination, Hard Coded Values A value that identifies where an item on the agreement is delivered. This required field must match the Destination Type code, as follows: o If the destination type is AB, the destination must be an address book number in the Address Book Master table (F0101). o If the destination type is CC, the destination must be a business unit in the Business Unit Master table (F0006). o If the destination type is A, the destination must be ANY.	Refer to Destination Type. Depends on Destination Type which instructs which file to read between F0101 (Address Book) and F0006 (Business Unit)
	DESY	DestinationType	Destination Type, UDC (38/DY) - Destination/Source Type A code that identifies the type of destination. Valid values are: AB The destination must be an Address Book number. CC The destination must be a business unit. *A The destination can be any location.
	SEQ*	SequenceNumber1	Sequence Number	F38012.SEQ = F38011.SEQ which is a member of primary key for F38011
	PSR*	ProductSource	Source, Hard Coded codes A value that identifies the location that supplies the item to fulfill the agreement. The value must match the Source Type code, as follows: o If the source type is AB, the transaction source must be an address book number in the Address Book Master table (F0101). o If the source type is CC, the transaction source must be a business unit in the Business Unit Master table (F0006). o If the source type A, the transaction source must be ANY.	Refer to DES
	PSRY*	ProductSourceType	Source Type, UDC (38/DY) - Destination/Source Type A code that specifies the type of source entered in the Transaction Source field, as follows: o If the transaction source is an address book number in the Address Book Master table (F0101), the source type must be AB. o If the transaction source is a business unit in the Business Unit Master table (F0006), the source type must be CC. o If the transaction source is ANY, the source type must be A.	Same with DESY
	CNQT	ContractQuantity	Contract Quantity, Display Rule CODE\|M - No commas - No Zero Bal-'-' The gross quantity for the life of the contract.	Note that quantity is describe without having negative sign and thousands commas
	AA	AmountFileld	Amount
	UOM	UnitOfMeasureAsInput	Unit of Measure as Input
	MINQ	QuantityMinimumTransacti	Quantity - Minimum Transaction, CODE\|2 - Commas - No Zero Bal - No Sign The minimum transaction quantity allowed for any transaction to fulfill the agreement. If you apply quantity control to the agreement, the system checks that each transaction meets the minimum allowed. If a transaction is entered for less than this quantity, a penalty can be assessed.
	MAXQ	MaximumQuantity	Quantity - Maximum Capacity, CODE\|4 - No Commas-No Zero Bal-No Sign The maximum of an item or item dimension group that can fit in the specified location dimension group. You can also define a storage container to limit the quantity.
	QBAL	BalanceQuantity	Balance Quantity Current balance of agreement transactions which have been posted.
	QCOM	CommittedQuantity	Committed Quantity Current balance of agreement transactions which have been committed.
	EFTJ	DateEffectiveJulian1	Date - Effective
	EXDJ	DateExpiredJulian1	Date - Expired	If you leave it blank the last day of CENTCHG value for year.
F38010	DL01	Description001	Description
	DMTC	ContractTypeDistribution	Agreement Type - Distribution, UDC 38/CV - Agreement Type A user defined code that indicates the general type of the agreement. C - Comingled Stock E - Exchange L - Loan and Borrows N - Consignment P - Purchase S - Sales T - Throughput
	DMSC	ContractStatusDistributi	Agreement Status, UDC 38/CU - Agreement Status A user defined code that indicates the current status of the agreement. A - Active C - Closed P - Pending	To enable be pulled the status must be 'A - Active'
	AN8	AddressNumber	Address Number	Either customer or supplier depends on Contract Type
	QEDT	EnforceQuantityEdits	Enforce Quantity Edits, Default Value 'Y' A code that determines whether you want the system to enforce quantity requirements when you assign an agreement number to a transaction. Valid values are: Y or 1: Yes, have the system verify that sufficient quantity remains on the agreement and that the transactions does not violate the minimum quantity. N or 0: Do not consider quantity when performing an edit of an agreement number. If you set Agreement Quantity Type to A for amount, the quantity control is not valid and this field must be either N or 0.	In P38010 value is defined as '0' or '1' which is different from default value defined in DD
	CAND	DateCancellation	Date - Cancellation of Contract
	UPGL	UpdateGeneralLedger	Update General Ledger Indicates when the system updates the general ledger. Valid values are: Y Journal entries will be written as soon as the quantity moves into this operation. N Journal entries will not be written at this time.
	PRAS	PriceatAmbiantorStandard	Price at Ambient/Standard/Weight (A,S,W), Default Value 'A', UDC 38/PR - Price at Ambient/Standard/Wt Identifies the price extension calculation method. Valid Values are: A Unit price X delivered volume at ambient temperature S Unit price X delivered volume at standard temperature W Unit price X delivered weight If the invoice is printed prior to delivery, the price extension calculation uses the order quantity in the pricing unit of measure. That is, ambient and standard quantity will be the same.
	CMOO	CommingledOtherOwner	Commingled Other Owner, Default Value 'N', Value either 'Y' for Yes or 'N' for No Indicates that the transaction uses commingled inventory and that it is for another owner. Journal entries will not be written for stock belonging to another owner.
	CNQY	ContractQuantityType	Contract Quantity Type, Default value 'Q', UDC 38/CN - Agreement Quantity Type A code that indicates if this agreement is based on quantity by item or currency amount. Valued values are: Q Quantity A Currency Amount If you specify Q, you can enter quantity and unit of measure for the products covered by the agreement. If you specify A, you can enter currency amounts covered by the agreement. The system calculates currency amounts on the price for sales order transactions or the cost for purchase transactions.	How to complete agreement between quantity and amount
F38011	SEQ	SequenceNumber1	SequenceNumber	F38012.SEQ is originated from F38011.SEQ
	AA	AmountFileld	Amount
	UOM	UnitOfMeasureAsInput	Unit of Measure as Input
	MINQ			Refer F38012.MINQ
	MAXQ			Refer F38012.MAXQ
	UPRC	AmtPriceUnit2	Amount - Price per Unit
	ASN	PriceAdjustmentScheduleN	Price and Adjustment Schedule
	MCU	CostCenter	Business Unit
	CRCD	CurrencyCodeFrom	Currency Code - From

Note:

The reading sequence has to be F38012, F38010 then F38011 so verify the relationship among three files
Primary Key of F38012 is DMCT, DMCS, SEQ, PSR, PSRY

Example of Callstack:
Note that the callstack below shows a simplified routine which only shows Agreement Related NERs or C Functions. For this example Sales Agreement is followed. Note that in update mode (when F4211.DMCT, F4211.DMCS) are already populated, then the process does not create cache for selection. Rather it validates exiting agreements based on existing values. It is always recommended to capture logs for both runtime and the call object kernel to determine how data is handled within a certain routine.

Case (New Order - Add Mode)

	Hook Up	Business Function				Source Code	Mode	Note
W4210A	Row is Exited/Changed - Async
		F4211FSEditLine				B4200310,	ActionCode = 'A' for ADD	This Master business function is to validate Sales Order detail and write cache/workfile which is to be used during End Doc routine
			F38010AgreementSearch			N3800050		This NER is to control process so actual transaction is handled by business functions called by this NER
				F38010AgreementCache		B3800070	cModeProcessing = '6' this is to initialize cache and terminate cache if any per Job Number	jdeCacheInit jdeCacheOpenCursor jdeCacheDeleteAll or, jdeCacheCloseCursor (when there is no cache to delete)
				F38012SearchMode		N3800050	cModeProcessing = '3'	Validation and Fetching Data from relevant files are handled by this NER. If P38200W did not show any cache data in it, then check this NER. Refer example of query in note below
					F38010AgreementCache	B3800070	cModeOfProcessing = '6' to delete exiting cache	jdeCacheInit jdeCacheOpenCursor jdeCloseCursor
					F38010AgreementCache	B3800070	cModeOfProcessing = '8' Fetch Full Key then Add cache B3800070	jdeCacheInit jdeCacheFetchPosition
				F38012SearchMode		N3800050
W38200WB	Last Grid Record Has Been Read
		F38010AgreementCache					cModeOfProcessing = '2' to get Cache which was created during F4211FSEditLine routine	WHILE loop (because there can be multiple agreements which meet condition Entering jdeCacheInit Entering jdeCacheOpenCursor jdeCacheFetchPosition

Note:

If there is any agreement met condition, a check mark will appear in the row header
If there are more than one agreement condition met, then write it into the grid through insert grid buffer row (this information can be traced through runtime log, namely, JASDEBUG)
Query to be issued (key can be vary),
- sql> SELECT * FROM PRODDTA.F38012 WHERE ( DPITM = 75392.000000 AND DPDTO = 'P' AND DPDES = '00004242' AND DPDESY = 'AB' AND DPPSR = ' 30' AND DPPSRY = 'CC' ) ORDER BY DPEXDJ DESC,DPDMCT ASC,DPDMCS ASC,DPSEQ ASC,DPPSRY ASC,DPPSR ASC
- sql> SELECT * FROM PRODDTA.F38010 WHERE ( DNDMCT = 'DMSEO01 ' AND DNDMCS = 1.000000 )
- sql> SELECT * FROM PRODDTA.F38011 WHERE ( DFDMCT = 'DMSEO01 ' AND DFDMCS = 1.000000 AND DFSEQ = 1.000000 )
Cache Name: B3800070A3 + mnJobNumber
Cache: hAgreementCache which (unique) key is made up of 12 elementes szComputerID, mnJobNumber, mnOrderNumber, szOrderType, szOrderCompany, szOrderSuffix, mnLineNumber, szAgreementNumber, mnAgreementSupplement, mnSequenceNumber, szAgreementSource and szAgreementType
For Cache action it follows standard JDE APIs

Case (Exiting Order - Update Mode)

	Hook Up	Business Function					Mode	Note
W4210A	Row is Exited/Changed - Async
		F4211FSEditLine (B3200310/B4200311)					Actin Code = 'C' for Change
			F38010FullEditMode				cModeProcessing = 1 for Add Mode cModeProcessing = 2 for Change Mode
				F38010AgreementSearch
					F38010AgreementCache			Delete cache
					F38012SearchMode
						F38010AgreementCache		Add cache
						F38010AgreementCache
					F38012SearchMode

Note:

For both Add Mode and Change mode it follows same routine, but with different cModeProcessing (or cache action code)
F38010FullEditMode gets called when Agreement Number is not blank during Edit Line routine
For this case it does not set a Check Mark in the row header, hence it shall not call P38200W application. In P4210 form W4210A Check Marks can appeared when Basket Order exists, Substitue Item exist, and/or Agreement exists

Data Structure:

* D3800050A : F38010 Agreement Search

Seq	Parameter	Data Type	Alias	I/O	Example	Mapping	Note
1	cDueTo	JCHAR	DTO	I	P		Hard Coded 'P' for Sales Agreement for example
2	mnIdentifierShortItem	MATH_NUMERIC	ITM	I	75392	Detail.mnShortItemNumber
3	szSource1[13]	JCHAR	SRC4	I	30		For intercompany assign Header MCU (otherwise Detail MCU)
4	szSourceType1[3]	JCHAR	SRCY4	I	CC		Hard Coded 'CC' for Sales Agreement
5	szSource2[13]	JCHAR	SRC5	I	00001		For intercompany assign Header KCOO (otherwise Detail KCOO)
6	szSourceType2[3]	JCHAR	SRCY5	I	AB		Hard Code 'AB" for Sales Agreement
7	szDestination1[13]	JCHAR	DES	I	00004242	Header.AN8 (Customer)	Convert it to string and '0' lpad
8	szDestinationType1[3]	JCHAR	DESY	I	AB		Hard Code 'AB" for Sales Agreement
9	szDestination2[13]	JCHAR	DES4	I		Header.SHAN (Ship To)	Only when Header.ShipTo <> Header.SoldTo
10	szDestinationType2[3]	JCHAR	DESY4	I			Hard Code 'AB" for Sales Agreement only when Ship To is different from Sold To
11	jdDate	JDEDATE	DTE	I	29/03/2012	Detail.jdRequestedDate
12	mnQuantity1	MATH_NUMERIC	QTY1	O	2.0000	Detail	mnQtyShipped + mnQtyBackOrdered
13	mnQuantity2	MATH_NUMERIC	QTY2	O			N/A
14	szUnitOfMeasure1[3]	JCHAR	UOM	I	EA	Detail.szTransactionUOM
15	szUnitOfMeasure2[3]	JCHAR	UOM2	I	EA	Detail.szPricingUOM
16	cAgreementSearchMethod	JCHAR	SRCH	I	2	cPOAgreementProcessing	Processing Option value for a specific version to run P4210
17	mnOrderNumber	MATH_NUMERIC	DOCO	I	1436		Primary Key for Sales Order
18	szOrderType[3]	JCHAR	DCTO	I	SO		Primary Key for Sales Order
19	szOrderCompany[6]	JCHAR	KCOO	I	00001		Primary Key for Sales Order
20	mnLineNumber	MATH_NUMERIC	LNID	I	1.0000		Primary Key for Sales Order
21	szProductSource[13]	JCHAR	PSR	O
22	szProductSourceType[3]	JCHAR	PRSY	O
23	szAgreementNumber[13]	JCHAR	DMCT	O
24	mnAgreementSupplement	MATH_NUMERIC	DMCS	O
25	mnSequenceNumber	MATH_NUMERIC	SEQ	O
26	mnAgreementsFound	MATH_NUMERIC	AFND	O
27	cSuppressError	MATH_NUMERIC	MATH01	O	1		1 - Not to stop though it hits error
28	mnJobnumberA	MATH_NUMERIC	JOBS	O	3	Detail.mnCMJobNo	This job number is originated from Edit Line routine
29	szComputerID[16]	JCHAR	CTID	O	MFGJAPAC02	Detail.szCMComputerID	This Machine Name is originated from Edit Line routine
30	szBaseCurrencyCode[4]	JCHAR	CRCD	O		Header.CRDC
31	szForeignCurrencyCode[4]	JCHAR	CRRP	O		Header.CRCD
32	mnAmountField	MATH_NUMERIC	AA	O
33	szOrderSuffix[4]	JCHAR	SFXO	O	000	HeaderCache.SFXO
34	szErrorMessage[11]	JCHAR	DTAI	O
35	cAccommodations	JCHAR	UPGL	O
36	cUpdateAmbStdWgt	JCHAR	PRAS	O
37	mnUnitPrice	MATH_NUMERIC	UPRC	O
38	szPriceSchedule[9]	JCHAR	ASN	O
39	cAgreementType	JCHAR	DMTC	O
40	mnPartner	MATH_NUMERIC	PTNR	O
41	cCommingled	JCHAR	CMOO	O
42	szUnitOfMeasurePricing[3]	JCHAR	UOM4	O
43	mnForeignUnitPrice	MATH_NUMERIC	FUP	O
44	szCostCenter[13]	JCHAR	MCU	O
45	cAccommodationAgreeOnly	JCHAR	EV02	O
46	cCurrencyToConvert	JCHAR	EV04	I	1
47	mnExchangeRate	MATH_NUMERIC	CRR	I		Header.CRR

* D3800050B : F38012 Search Mode (assigned by calling routine N3800050 - F38010AgreementSearch)

Seq	Parameter	Data Type	Alias	I/O	Example	Mapping	Note
1	cModeProcessing	JCHAR	MODE	I	Same with above mapping	Values from calling routine	Depends on values (source and destination) specifice in calling routine possible values are, 1 = by Destination 2 = by Source 3 = by Source/Destination
2	cDueTo	JCHAR	DTO	I
3	mnIdentifierShortItem	MATH_NUMERIC	ITM	I
4	szDestination[13]	JCHAR	DES	I
5	szDestinationType[3]	JCHAR	DESY	I
6	jdDate	JDEDATE	DTE	I
7	mnQuantity1	MATH_NUMERIC	QTY1	I/O
8	mnQuantity2	MATH_NUMERIC	QTY2	I/O
9	szProductSource[13]	JCHAR	PSR	I/O
10	szProductSourceType[3]	JCHAR	PSRY	I/O
11	szUnitOfMeasure1[3]	JCHAR	UOM	I/O
12	szUnitOfMeasure2[3]	JCHAR	UOM2	I/O
13	cAgreementSearchMethod	JCHAR	SRCH	I/O
14	mnSequenceNumber	MATH_NUMERIC	SEQ	I/O
15	mnOrderNumber	MATH_NUMERIC	DOCO	I/O
16	szOrderType[3]	JCHAR	DCTO	I/O
17	szOrderCompany[6]	JCHAR	KCOO	I/O
18	mnLineNumber	MATH_NUMERIC	LNID	I/O
19	szCostCenter[13]	JCHAR	MCU	I
20	szAgreementNumber[13]	JCHAR	DMCT	I/O
21	mnAgreementSupplement	MATH_NUMERIC	DMCS	I/O
22	mnAgreementsFound	MATH_NUMERIC	AFND	I/O
23	jdEarliestExpirationDate	JDEDATE	EXDJ	I/O			Today's date through B4000630 (VerifyEffectiveDates) because input effective date is NULL Date
24	mnJobnumberA	MATH_NUMERIC	JOBS	I/O
25	szComputerID[16]	JCHAR	CTID	I/O
26	szSource1[13]	JCHAR	SRC4	I/O
27	szSourceType1[3]	JCHAR	SRCY4	I/O
28	szBaseCurrency[4]	JCHAR	CRCD	I
29	mnAmountField	MATH_NUMERIC	AA	I/O
30	szOrderSuffix[4]	JCHAR	SFXO	I/O
31	szErrorMessage[11]	JCHAR	DTAI	O
32	cAccommodations	JCHAR	UPGL	I/O
33	cUpdateAmbStdWgt	JCHAR	PRAS	I/O
34	mnUnitPrice	MATH_NUMERIC	UPRC	I/O
35	szPriceSchedule[9]	JCHAR	ASN	I/O
36	cAgreementTypeDistribution	JCHAR	DMTC	I/O
37	mnPartner	MATH_NUMERIC	PTNR	I/O
38	cCommingled	JCHAR	CMOO	I/O
39	szUnitOfMeasurePricing[3]	JCHAR	UOM4	I/O
40	szForeignCurrencycode[4]	JCHAR	CRDC	I
41	mnForeignUnitPrice	MATH_NUMERIC	FUP	I/O
42	cAccommodationAgreeOnly	JCHAR	EV01	I
43	cSuppressError	JCHAR	ERR	I		1 to suppress error	This flag follows calling routine in N3800050
44	cCurrencyToConvert	JCHAR	EV04	I
45	mnExchangeRate	MATH_NUMERIC	CRR	I

Note: Each parameter repeats the same parameter from calling routine N3800050 - F38010AgreementSearch

* D3800050C : F38010 Full Edit Mode (mapped by Edit Line MBF routine. e.g., F4211FSEditLine). Mapping is same with D3800050A

Seq	Parameter	Data Type	Alias	I/O	Example	Mapping	Note
1	cModeProcessing	JCHAR	MODE	I	2	Hard Coded	1 - when cCMLineAction is A - Add Mode 2 - when cCMLineAction is C - Change Mode
2	cDueTo	JCHAR	DTO	I	P	Hard Coded	Refer Data Structure D3800050A for columns below
3	mnIdentifierShortItem	MATH_NUMERIC	ITM
4	szSource1[13]	JCHAR	SRC4
5	szSourceType1[3]	JCHAR	SRCY4
6	szSource2[13]	JCHAR	SRC5
7	szSourceType2[3]	JCHAR	SRCY5
8	szDestination1[13]	JCHAR	DES
9	szDestinationType1[3]	JCHAR	DESY
10	szDestination2[13]	JCHAR	DES4
11	szDestinationType2[3]	JCHAR	DESY4
12	jdDate	JDEDATE	DTE
13	mnQuantity1	MATH_NUMERIC	QTY1
14	mnQuantity2	MATH_NUMERIC	QTY2
15	szUnitOfMeasure1[3]	JCHAR	UOM
16	szUnitOfMeasure2[3]	JCHAR	UOM2
17	cAgreementSearchMethod	JCHAR	SRCH
18	szAgreementNumber[13]	JCHAR	DMCT
19	mnAgreementSupplement	MATH_NUMERIC	DMCS
20	mnSequenceNumber	MATH_NUMERIC	SEQ
21	szProductSource[13]	JCHAR	PSR
22	szProductSourceType[3]	JCHAR	PSRY
23	mnOrderNumber	MATH_NUMERIC	DOCO
24	szOrderType[3]	JCHAR	DCTO
25	szOrderCompany[6]	JCHAR	KCOO
26	mnLineNumber	MATH_NUMERIC	LNID
27	mnUnitPrice	MATH_NUMERIC	UPRC
28	cAgreementType	JCHAR	DMTC
29	szUnitOfMeasurePricing[3]	JCHAR	UOM4
30	mnAmountField	MATH_NUMERIC	AA
31	szBaseCurrencyCode[4]	JCHAR	CRCD
32	szForeignCurrencyCode[4]	JCHAR	CRDC
33	mnForeignPrice	MATH_NUMERIC	FUP
34	szDepot[13]	JCHAR	MCU
35	mnAgreementsFound	MATH_NUMERIC	AFND
36	szPriceAdjustmentScheduleN[9]	JCHAR	ASN
37	mnJobnumberA	MATH_NUMERIC	JOBS
38	szComputerID[16]	JCHAR	CTID
39	szOrderSuffix[4]	JCHAR	SFXO
40	szErrorMessage[11]	JCHAR	DTAI
41	cAccommodations	JCHAR	UPGL
42	cUpdateAmbStdWgt	JCHAR	PRAS
43	mnPartner	MATH_NUMERIC	PTNR
44	cCommingled	JCHAR	CMOO
45	cAccommodationAgreeOnly	JCHAR	EV01
46	cSuppressError	JCHAR	ERR
47	cCurrencyToConvert	JCHAR	EV04
48	mnExchangeRate	MATH_NUMERIC	CRR

* D3800050D : F38010 Delete Agreement Cache

Seq	Parameter	Data Type	Alias	I/O	Example	Mapping	Note
1	mnJobnumberA	MATH_NUMERIC	JOBS	I	3	Same Job Number with calling Master Business Function	Key for Agreement Cache. In thin client configuration (where BSFN is running in Server) Job Number may be represented as 1003
2	szComputerID[16]	JCHAR	CTID	I	MFGJAPAC02	Same machine ID with master business function routine	Key for Cache
3	cModeProcessing	JCHAR	MODE	I	7	cModeProcessing '7' to delete all the caches during a certain process	Hard Coded in Calling then look for cache which was created via B3800070 to delete/terminate all

* D3800070 : F38010 Agreement Cache (N3800050 - F38012SearchMode handled Agreement Cache)

Seq	Parameter	Data Type	Alias	I/O	Example	Mapping	Note
1	mnJobNumber	MATH_NUMERIC	JOBS	I	3	= F4211FSEditLine.mnCMJobNumber
2	szComputerID[16]	JCHAR	CTID	I	MFGJAPAC02
3	mnOrderNumber	MATH_NUMERIC	DOCO	I	1436
4	szOrderType[3]	JCHAR	DCTO	I	SO
5	szOrderCompany[6]	JCHAR	KCOO	I	00001
6	szOrderSuffix[4]	JCHAR	SFXO	I	000
7	mnLineNumber	MATH_NUMERIC	LNID	I	1.000
8	szAgreementNumber[13]	JCHAR	DMCT	O
9	mnAgreementSupplement	MATH_NUMERIC	DMCS	O
10	mnSequenceNumber	MATH_NUMERIC	SEQ	O
11	szAgreementSource[13]	JCHAR	PSR	O
12	szAgreementType[3]	JCHAR	PSRY	O
13	cAgreementDistribution	JCHAR	DMTC	O
14	szAgreementDescription[31]	JCHAR	DL01	O
15	jdEffectiveDate	JDEDATE	EFTJ	O
16	jdExpiredDate	JDEDATE	EXDJ	O
17	szItemNoUnknownFormat[27]	JCHAR	UITM	O
18	mnAgreementQuantity	MATH_NUMERIC	CNQT	O
19	mnBalanceQuantity	MATH_NUMERIC	QBAL	O
20	mnCommittedQuantity	MATH_NUMERIC	QCOM	O
21	cDueTo	JCHAR	DTO	O
22	szDepot[13]	JCHAR	MCU	O
23	szDestination[13]	JCHAR	DES	O
24	szDestinationType[3]	JCHAR	DESY	O
25	cUpdateGL	JCHAR	UPGL	O
26	cUpdateAtAmbiantStandardW	JCHAR	PRAS	O
27	mnOverridePrice	MATH_NUMERIC	UPRC	O
28	szPriceSchedule[9]	JCHAR	ASN	O
29	mnPartner	MATH_NUMERIC	PTNR	O
30	szUnitOfMeasure[3]	JCHAR	UOM	O
31	szCurrencyCode[4]	JCHAR	CRCD	O
32	cErrorCode	JCHAR	ERRC	O
33	idGenericLong	ID	GENLNG	O
34	cRecordFound	JCHAR	EV01	O
35	cModeProcessing	JCHAR	MODE	I			cModeProcessing 1- ADD 2 - GET - Fetch based on the cursors 3 - full key update 4 - get next 5 - Update 6 - delete record based on a partial key with 7 fields 7 - DELETE - ALL 8 - FETCH FULL KEY 9 - Terminate the cache
36	cCommingledOtherOwner	JCHAR	CMOO	O
37	mnAmtForPricePerUnit	MATH_NUMERIC	FUP	O

Note:

The flow of cModeProcessing which controls the process of cache are,
- 6 (delete record based on a partial key with 7 fields) to create a new cache
- 8 (FETCH FULL KEY) to check whether there is any existing cache
- 1 (Add) to add a new cache
- 2 (Get) to verify cache created
- ...
- 9 (Terminate the cache) to nullify cache used in transaction

Case Study:
A possible question might be: "Why does P38200W not show any information in the grid?".

In case your system failed to show Agreement Information in W38200WB form:

Check data from F38012, F38010 and F38011 in sequence
Check whether key fields are populated correctly
Check whethe cache has handled correctly or not
If possible, capture callobject kernel log (jdedebug.log) for your test and debug it

This document is written based on application release 9.1