This note is to explain business functions can be implemented through R00460 - Interoperability Generic Outbound Subsystem UBE.
This document is to explain possible issue you may face in dealing with a report R00460 - Interoperability Generic Outbound Subsystem UBE. Currently this report is made up of 2 sections as below,
1st. Section "Load Processing Log" (no Business View) which writes F0046 conditionally
2nd. Section "Processing Log - Outbound Subs" (based on Business View V0046B which is joined view between F0046 and F0047) which may call Vendor's UBE or BSFN to extract Outbound Interoperability table data depending on the setup you are on
This document is made up of,
Primary Keys of table related
Related Business Functions
Primary Key for tables related: Individual Table possibly give you better idea to get the purpose of each tables
Purpose: This business function is to populate data from F0046 depends on your business requirement through R00460 which is to be handled by subsystem kernel. Data are to be populated only when some of setup is done correctly (refer to <Document 1342363.1> - E1:31: How to implement Work Order Extraction through R00460 in P48013)
Parameter
Data Structure: B0000195A - Create Processing Log Records
Parameter Name
Data Item
Data Type
I/O
Req
Purpose
szUserId[11]
EDUS
JCHAR
I
Y
* Primary Key. User ID for the user who edits any transaction which has interoperability interface
szBatchNumber[16]
EDBT
JCHAR
I
Y
* Primary Key of F0046
szTransactionNumber[23]
EDTN
JCHAR
I
Y
*
mnLineNumber
EDLN
MATH_NUMERIC
I
Y
*
szTransactionType[9]
TYTN
JCHAR
I
Y
*
szOrderType[3]
DCTO
JCHAR
I
Y
*
szTransactionAction[3]
TNAC
JCHAR
I
Y
cErrorEncountered
ERR1
JCHAR
O
Detail Routine:
I0000195_CheckIfF0046RecordsExist: If record does exist, exit from routine
(when data do not reside from F00460) I0000195_CreateF0046Records
Validate szTransactionAction through BSFN N0000179 - TNACConvertToActionCode (Transaction Action, Convert To Action Code) to get the 1st Character of Description 02 from UDC 00/TA - Transaction Action. For example, if szTransactionAction is 02 the first character of UDC 00/TA is 'A' which determines Add of data. Currently valid action codes are 'A - Add', 'D - Delete', 'I - Inquiry', 'C - Change', 'R - Replace' and 'U - Update'.
While loop to read data from F0047 based on 1st 2 columns (F0047.TYTN and F0047.DCTO) to check existence of F0047 (and if any) to return F0047.SEQ, OBNM, VERS
Insert data into F0046
Call B0000194 - UpdateUneditedTransactionTableAs (Update Unedited Transaction Table As Processed)
2. B0000194 - UpdateUneditedTransactionTableAs (Update Unedited Transaction Table As Processed)
Purpose: This business function is to update/set InteropTable.EDSP='Y' after getting F47002.FILE (=InteropTable) when definition for a specific Transaction Type is defined at F47002 - Flat File Cross-Reference File where F47002.TYTN = 'szTypeTransaction' AND F47002.DRIN = '&cOutBoundDir' (&cOutBoundDir='2').
Parameter
Data Structure: B0000194 - Update Unedited Transaction Table As Processed
Parameter Name
Data Item
Data Type
I/O
Req
Purpose
szTypeTransaction[9]
TYTN
JCHAR
I
Y
Type Transaction (e.g., JDEWO)
szUserId[11]
EDUS
JCHAR
I
Y
szBatchNumber[16]
EDBT
JCHAR
I
Y
szTransactionNumber[23]
EDTN
JCHAR
I
Y
mnLineNumber
EDLN
MATH_NUMERIC
I
Y
cErrorEncountered
ERR1
JCHAR
O
Detail Routine:
1. Read F47002 and return F47002.FILE sql> SELECT SVTYTN, SVDRIN, SVEDTY, SVFILE FROM PRODDTA.F47002 WHERE ( SVTYTN = 'JDEWO' AND SVDRIN = '2' ) ORDER BY SVEDTY ASC 2. Update InteropTable.EDSP = 'Y' sql> UPDATE PRODDTA.F4801Z1 SET SYEDUS='SDONGMYE',SYEDBT='0',SYEDTN='125918',SYEDLN=2000.000000,SYEDSP='Y' WHERE ( SYEDUS = 'SDONGMYE' AND SYEDBT = '0' AND SYEDTN = '125918' AND SYEDLN = 2000.000000 ) : If F47002 does not have proper definition EDSP will be remained as unsuccessfully
Purpose: This function is designed to launch the Interoperability Vendor-Specific UBE specified in the Input Parameter's UBE Name and Version. It will also pass 6 additional parameters to the Vendor-Specific UBE, namely EDI User ID(EDUS), EDI Batch Number(EDBT), Transaction Number (EDTN), Export Mode Flat File(FFEM), Export Mode Database(EDEM) and Export Mode API(EAEM). After the Vendor-Specific UBE returns, it will copy the UBE Error Code parameter from the Vendor-Specific UBE's report interconnect data structure to the Output Error Code parameter. Vender-Specific UBE is to be called through jde API jdeLaunchUBEEx() synchronously.
Parameter
Data Structure: D0000178 - Interoperability, Launch Vendor-Specific UBE
Parameter Name
Data Item
Data Type
I/O
Req
Purpose
szVendorSpecificUBEName[11]
OBNM
JCHAR
I
F0046.OBNM which you have defined through P0047 (=F0047.OBNM)
szVersionToCall[11]
VERS
JCHAR
I
F0046.VERS (=F0047.VERS)
szEdiUserId[11]
EDUS
JCHAR
I
F0046.EDUS
szEdiBatchNumber[16]
EDBT
JCHAR
I
F0046.EDBT
szEdiTransactionNumber[23]
EDTN
JCHAR
I
F0046.EDTN
cExportModeFlatFile
FFEM
JCHAR
N/A
cExportModeDatabase
EDEM
JCHAR
N/A
cExportModeAPI
EAEM
JCHAR
N/A
cUBEErrorCode
ERRC
JCHAR
N/A
cErrorCode
ERRC
JCHAR
N/A
mnEdiLineNumber
EDLN
MATH_NUMERIC
I
F0046.EDLN
Detail Routine: Arguments are determined by V0046B - 'Processing Log - Outbound Subsystem UBE' which is table joins between F0046 and F0047 (respectively Processing Log and Data Export Control).
This function gets called from R00460 only when F0047.LCIM (Launch Immediately) is turned on (value 1). In caes this value is 0 to proceed extraction R00461 has to be run either mannually or through scheduler.
Special Logic:
1. All required fields must be passed in. 2. The Vendor-Specific UBE called by this business function must have the following Report Interconnect data structure. The order of the parameters in the UBE data structure must be maintained as follows (though argument may be null): EDI User ID(EDUS) (INPUT) EDI Batch Number (EDBT) (INPUT) EDI Transaction Number (EDTN) (INPUT) Export Mode Flat File (FFEM) (INPUT) Export Mode Database (EDEM) (INPUT) Export Mode API (EAEM) (INPUT) UBE Error Code (ERRC) (OUTPUT)
3'. B0000192 - CallVendorSpecificFunctionOut (Call Vendor-Specific Function - Outbound)
Purpose: This function is designed to call custom (or vendor-specific) function to extract interoperability data per your business requirement.
Parameter
Data Structure: D0000192A - Call Vendor-Specific Function - Outbound
Parameter Name
Data Item
Data Type
I/O
Req
Purpose
szFunctionName[51]
FCNN
JCHAR
I
Y
F0047.FCNN
szFunctionLibrary[257]
FCNL
JCHAR
I
Y
F0047.FCNL
szUserId[11]
EDUS
JCHAR
I
Y
F0046.EDUS
szBatchNumber[16]
EDBT
JCHAR
I
Y
F0046.EDBT
szTransactionNumber[23]
EDTN
JCHAR
I
Y
F0046.EDTN
mnLineNumber
EDLN
MATH_NUMERIC
I
Y
F0046.EDLN
szTransactionType[9]
TYTN
JCHAR
I
Y
F0046.TYTN
szDocumentType[3]
DCTO
JCHAR
I
Y
F0046.DCTO
mnSequenceNumber
SEQ
MATH_NUMERIC
I
Y
F0046.SEQ
cErrorsEncountered
ERR1
JCHAR
O
Detail Routine:
Load library through API LoadLibrary() else, set error "096G - Cannot open/initialize DLL"
Retrieve the address of the vendor function through API jdeGetProcAddress() else, set error "096G - Cannot open/initialize DLL"
Call the vendor function through API VendorFnctIn ()
Note:
We, Oracle, do not provide any custom code and do not bear result you get through this implementation
<Document 626628.1> - E1: BSFN: Business Function and API DocumentationJD Edwards EnterpriseOne Tools 8.98 Development Tools: APIs and Business Functions Guide