R6 Interface Setup

This section describes any changes that must be made as a customer converts to V6. 

Adjustments needed for PO Approval:
1) RPGLE K3S_1050--Adjust the parameters passed when calling K3S_1100. 

(***This program is used in production; plan ahead before compiling as users will be actively using this program***)

The parameters passed to K3S_1100 should be:

COMP       1A   
BUYR        5A   
LOCN        5A
SUPL        10A
SUPLSUB    10A
SOQSEQN  5,0
POMSG1    25A
POMSG2    25A
POMSG3    25A
POMSG4    25A
POMSG5    25A
POMSG6    25A
POMSG7    25A
PRTHERE   1A
PODATE    d datfmt(*ISO)
ARVDATE    d datfmt(*ISO)
POBLANK    10A
POTYPE        1A
LOCNFRM    5A
LOCNTO        5A
WORKSTN    10A
HOLDBEG        d datfmt(*ISO)
HOLDEND       d datfmt(*ISO)
HLDREAS        40A
SKIPLT        1A
USER        10A 
USERA01    1A
USERA02    1A
USERA03    1A
USERA04    1A
USERA05    5A
USERA06    5A
USERA07    10A
USERA08    10A
USERA09    100A
USERA10    100A

2) RPGLE K3S_1100--Adjust the incoming parameters and adjust the parameters passed to K3S_1101CL. 

(***This program is used in production; plan ahead before compiling as users will be actively using this program***)

The parameters passed to K3S_1100 should be:

COMP       1A   
BUYR        5A   
LOCN        5A
SUPL        10A
SUPLSUB    10A
SOQSEQN  5,0
POMSG1    25A
POMSG2    25A
POMSG3    25A
POMSG4    25A
POMSG5    25A
POMSG6    25A
POMSG7    25A
PRTHERE   1A
PODATE    d datfmt(*ISO)
ARVDATE    d datfmt(*ISO)
POBLANK    10A
POTYPE        1A
LOCNFRM    5A
LOCNTO        5A
WORKSTN    10A
HOLDBEG        d datfmt(*ISO)
HOLDEND       d datfmt(*ISO)
HLDREAS        40A
SKIPLT        1A
USER        10A 
USERA01    1A
USERA02    1A
USERA03    1A
USERA04    1A
USERA05    5A
USERA06    5A
USERA07    10A
USERA08    10A
USERA09    100A
USERA10    100A
   
When calling K3S_1101CL, add 10 parms to the end of the list to account for USERA01 - USERA10

3) CLLE K3S_1101CL--Adjust the incoming parameters, and (optional) adjust the parameters passed to the custom program that writes the PO to the customer's interface files. 

(***This program is used in production; plan ahead before compiling as users will be actively using this program***)

Add 10 parms to the end of the list to account for USERA01 - USERA10:

USERA01    1A
USERA02    1A
USERA03    1A
USERA04    1A
USERA05    5A
USERA06    5A
USERA07    10A
USERA08    10A
USERA09    100A
USERA10    100A

Additionally, pass the additional 10 parms for USERA01 - USERA10 to the RPGLE program that writes the PO information to the customer's system. This change is only necessary if the customer is passing valid information in the USERA01 - USERA10 fields. 

4) Custom RPGLE program -- This change is only necessary if the customer is passing valid information in the USERA01 - USERA10 fields. Adjust the RPGLE program that writes the PO to the customer's ERP system to accept 10 additional incoming parms for USERA01 - USERA10.  This program is typically called something like: K3S_PUT_PO, K3S_CRTPO, etc. 

5) CLLE K3S_7020CL--This is a NEW program that will call RPGLE program K3S_POPARM.  API AR_PODORDR calls 
K3S_7020CL to receive the next PO#, PO type, arrival date, as well as any default values for customized fields on the PO header screen.  Ensure the object exists in the 5MOD library, but likely no adjustments are needed for this program. 

6) RPGLE K3S_POPARM--This is a NEW program that will return the necessary values to populate the PO header screen, such as next PO#, PO type, arrival date, as well as any default values for customized fields on the PO header screen. This program mimics the function of K3S_5MOD/K3S_1050, i.e. any modifications made to K3S_1050 should be made to this program.  

7) RPGLE K3S_POCHCK--This is a NEW program that will validate the custom parameters on the PO approval screen, should the customer have any modifications to their PO approval screen. An error code will be returned if the user enters an invalid choice in a custom field. 

This program will be called by AR_APRORDR. The parameters passed should be:

COMP            1A
COMPCOD    3A
USER            10A
ERRORS        1A
ERRMSG        100A
ERRFLD        20A   
BUYR        5A   
LOCN        5A
SUPL        10A
SUPLSUB    10A
SOQSEQN  5,0
PONUMBER 10A
USERA01    1A
USERA02    1A
USERA03    1A
USERA04    1A
USERA05    5A
USERA06    5A
USERA07    10A
USERA08    10A
USERA09    100A
USERA10    100A

8) If the customer has custom fields on the PO approval screen, adjust table code type APR.  For each value listed, Flag1 = 1 to enable the field for use on the screen. Set Flag2 = 1 to require the fields for PO approval.  If FLAG2 = 0, then the user does not have to specify a value for this field in order to allow PO approval. 

Adjustments needed for Night job:
1) Create a new job description so that you can control the automatic reply function for a specific error. A PDF document is available for download below. 
2) Assign night job to the new JOBD
3) Exit point adjustments and adjustment to K3S_NIGHT to handle persistent locks 
4) Copy the API objects to the 5OBJ library (AC_*, AL_*, and TS_*)
5) Add the 5WEB library
6) Add XXXWEB to file K_USERPRF
7) Add files to the database (night job totals, buyer totals, etc)


Miscellaneous adjustments:
1) Ensure library 5WEB is added to the backup process. 
2) If the customer buys from diverters, see if they have a scheduled job to get the diverter offerings. Typically the job is named something similar to K3S_5GTALT.  Consider deleting this job and instead having CLLE program K3S_9110CL calling the program that the scheduled job was running.  The reason is because of the persistent database locks that can remain from Black Bean use. 



Ċ
Brantley May,
Dec 8, 2016, 6:51 AM
Comments