| Goal |
| Solution |
How does Advance Preference #40 (Generic Match) work? Need to know what the job number and job sequence number are. These are the fields referred to in the advanced preference detail UDC. We need a way to populate the matching field with a value from F4211. Is this possible?
This Generic Match Advance Preference (Preference Type 40) determines what information will be populated to the Sales Order Detail Customer Ledger Generic Key field (F4211.CLGM). The preference is driven by the normal hierarchical fields (customer, customer group, item, item group) and branch/plant. The return field will be a value between 1 and 9 corresponding to the list below.
Based on this value, the generic match field will be built as described in the list.
Below are the 9 supported combination's of data (listed in the glossary for dd item CLGM) listed below:
1= Job Number
2= Job Number + Job Sequence Number
3= Job Number + Customer Item Number
4= Job Sequence Number
5= Job Sequence Number + Job Number
6= Job Sequence Number + Customer Item Number
7= Customer Item Number
8= Customer Item Number + Job Number
9= Customer Item Number + Job Sequence Number
The Job Number and Job Sequence Number are Demand Scheduling Module (DSE)/Transportation Management Module (TMS) Sequencing specific. The generic match preference was designed in this manner to allow additional data combination's to be added to the preference as return values and into the B4280030 as a custom coded solution to return the data combination related to the new Advanced Preference value.
The Generic Match Preference will work without DSE, but only when the Customer Item number (7) is being used as the generic match. The Generic Match preference will get resolved only when the Level Break is set to 'None' in the Advanced Preference Definition and only two different hierarchies can be used: Customer only and all items/all customers is used. Any other combination (Customer group/item group, item/customer etc) will not work. Although Advanced Preference 40 is a DSE preference, it will work for regular sales orders and only the customer item number will get updated to the Customer Ledger Receipt Matching Reference 1 (F03B11.RMR1) field.
All of the other values from the generic match advanced preference require TMS Sequencing with DSE. The user could customize this advanced preference to return additional values besides 1-9, but they would need to customize the code as well to handle any additional return values.
For Advanced Preference '40' to work properly, setup is required in the Preference Values Maintenance (P40711) application as follows:
Row1:
Preference Record Type - 1
Advanced Preference Type - 40
Display Seq - 10
Data Item - MCU
R Y/N - Y
Data Structure Position - .00
Row2:
Preference Record Type - 2
Advanced Preference Type - 40
Display Seq - 20
Data Item - CLGM
R Y/N - Y
Data Structure Position - 1.00
Clarification for standard Sales Orders:
Based on Bug 11027892 : CUSTOMER LEDGER RECEIPT MATCHI - SAR: 8946933 - The advanced preference 40 (Customer Ledger Generic Match) will get resolved even for an SO which is not created from Demand Scheduling (DSE). In this case only Customer Item number generic match can be populated to RMR1 field in F03B11. This is because job number and job sequence number will be blank in the Sales Order Detail Tag file (F49211) for a normal SO. Job Number and Job sequence number will be populated in F49211 only in the case of SO created from DSE.
In the case of normal SO only customer item number will get updated to F03B11.RMR1 field by Sales Update (R42800). For this
1. Item customer cross reference should be set.
2. R42800 PO cross reference should be set to appropriate value as set in the item cross reference.
3. The customer ledger generic key should be for item number in preference detail.
With the above set up the RMR1 field in F03B11 will get updated for a normal SO.