From the Item Price Groups (P4092), click Add. Users may specify up to ten Category Codes.
For stock items, the Category Codes used in Item Price Group are the same Category Codes found in the Item Branch/Plant (P41026) off menu G4111.
| Purpose |
| Details |
| Item Price Groups (P4092) |
| Customer Price Groups (P4092) |
| Order Detail Groups (P4092) |
| Notes |
| Frequently Asked Questions |
| Question 1: User is getting Blanks Invalid error (0003) in the Price Detail (P4072) when they do not enter a value in the category code field when using complex groups. |
| Question 2: Customer is upgrading from XE to 9.1. The fields SDGR,SDV1,SDV2,SDV3, FRAT, RATT are used in V4072A in XE. In E9.1 these fields are deleted. What is the replacement for these fields? |
Overview
Complex groups can be used to provide more flexibility in a pricing structure. Category codes are used to set up the complex groups. There are 3 types of complex groups: Item, Customer, and Order Detail groups.
Complex Prices Groups are created using P4092 from menu G42311. The processing option behind the P4092 determines what type of group will be set up.
Item price groups can be setup using the program P4092, version ZJDE0001 off menu G42311.
From the Item Price Groups (P4092), click Add. Users may specify up to ten Category Codes.
For stock items, the Category Codes used in Item Price Group are the same Category Codes found in the Item Branch/Plant (P41026) off menu G4111.
NOTE: If the item is a non-stock item, the Item Master Category Code fields will be used
Before adding the Price Adjustment Definition, select a Preference Hierarchy (P40073) where the Item Group is used.
Setup Price Adjustment Definition (P4071)
The Item Price Group name must be attached to the Price Adjustment Definition (P4071).
Note: Enhancement Bug 10962721 has been entered requesting that a complex group should not need to be added via P4071 to work.
The values in the Item Branch category codes must match the category code values in the Adjustment Details for the adjustment to be applied. The second screen below shows the 'Item Price Group' field in the 'Additional Info' tab of the Item Branch record (P41026), which can be left blank or populated with another Item Price Group - this field is used in conjunction with Simple Groups, which do not use Category codes.
Setup Adjustment Detail (P4072)
The Item Group Category Codes are required fields in the adjustment detail. Blank is not a valid value in the adjustment detail even though blank may be a valid value in the UDC table.
Sale Order Entry (P4210)
Enter a Sales Order with the Price Adjustment Schedule attached.
Price History (P4074)
Price History (P4074) will show the adjustment.
Generate Item Price Groups (R40931)
For EnterpriseOne users, it is not mandatory to run the Generate Item Price Groups (R40931) UBE in order to use the Item Price Group. This UBE creates records in the Item/Customer Group Relationship (F4093) table with a "Group Type" (GPTY) value of "I". This table contains the allowable combinations for Item Groups and Category Codes.
Item Group Code (P4093)
Once the R40931 UBE has been run, the user may access this table as an Item Group Code Row Exit off of the Price Adjustment Detail (P4072). The option will not appear unless the UBE has been executed.
Or, this can also be accessed from Base Price Revisions (P4106). The information displayed shows all the Category Codes selected for the Item Group and all the valid values for the Category Codes.
Customer Price Groups can be added using the P4092, version ZJDE0002 off menu G42311.
From the Customer Price Groups (P4092), click Add. Users may specify up to ten Category Codes.
The Category Codes used by the Customer Price Groups are the same Category Codes found in the Customer Master (P03013) on menu G4241.
Before adding the Price Adjustment Definition, select a Preference Hierarchy (P40073) where Customer Group is used. The customer group can be for either the Ship To or Sold To.
Setup Price Adjustment Definition (P4071)
The Customer Price Group name must be attached to the Price Adjustment Definition (P4071).
The values in the Customer Master category codes must match the category values in the Adjustment Details for the adjustment to be applied. The second screen below shows that the Customer Billing Instructions (P03013) can be left blank or populated with another Customer Price Group.
Setup Adjustment Detail (P4072)
The Customer Group Category Codes are required fields in the adjustment detail. Blank is not a valid value in the adjustment detail even though blank may be a valid value in the UDC table.
Sale Order Entry (P4210)
Enter a Sales Order with the Price Adjustment Schedule attached.
Price History (P4074)
Price History (P4074) will show the adjustment.
The Customer Group can be either the Ship To or Sold To.
Generate Customer Price Groups (R40932)
For EnterpriseOne users, it is not mandatory to run the Generate Customer Price Group (R40932) UBE in order to use the Customer Price Group. This UBE creates records in the Item/Customer Group Relationship (F4093) table with a "Group Type" (GPTY) value of "C". This table contains the allowable combinations for Customer Groups and Category Codes.
Customer Group Code (P4093)
Once this UBE has been run, the user may access this table as a Customer Group Code Row exit off of the Price Adjustment Detail (P4072).
Or, this can also be accessed via Base Price Revisions (P4106). The information displayed shows all the Category Codes selected for the Customer Group and all the valid values for the Category Codes.
Order Detail Groups are setup using the P4092, version ZJDE0003 off menu G42311.
To add an Order Detail Group users may select up to 8 Category Codes. The information on the Order Detail Group pertains to the Sales Order. The values used in the adjustment detail will be matched to the values defaulted (via preference) or manually entered into the Sales Order.
Although the name order detail group might seem to indicate an Order level adjustment, the adjustment is applied at the line level. Therefore each individual line on the sales order must meet the order detail requirement in order to receive the price adjustment.
Price Adjustment Definition (P4072)
The Order Detail Group must be specified on the price adjustment definition.
There is no specific Preference Hierarchy for Order Detail Groups.
Price Adjustment Detail information must match the information in the sales order detail line. For example, the adjustment detail is setup so that a discount is received if the Sales Order is an 'SO' Order Type and Branch/Plant 30 is used for the detail line.
Enter a Sales Order using the Price Adjustment.
Adjustment is applied.
Using Date Effective Category Codes with Line of Business Turned Off
Customers might want to select the Date Effective Category Code option on the P0009 Enhanced A/R Constants form with Advanced Pricing. Customer Category Codes in the Advanced Pricing system are used to specify the customer group and pricing on sales orders. By selecting this option, multiple sets of category codes for a single customer can be set-up by effective date. This enables the Advanced Pricing system to adjust the pricing based on the effective date for each customer group. If using Date Effective Category Codes, the system reads table F03012A and not F03012.
If system is defined/activated to use Date Effective Category Codes within the Enhanced A/R Constants (Accounts Receivable Constants) the Category Codes selection from the Form menu on P03013; Customer Master Revisions cannot be used to add, change or update the category code values as all category code fields will be grayed out. Instead, updates/changes need to be entered in the Date Effective Category Codes selection and then program R03012A ran to update F03013 Customer Master Category Codes.
The General Constants (F0009) table can be reviewed to confirm if system is set up to use customer category code values by effective date.
With the Date Effective Category Code option, the system displays row and form menu options from the Customer Master application that enable you to set up category codes with effective dates. If you do not select this option, the system hides these menus.
When adding a Date Effective Category Code value, this creates a record in the Customer Date Effective Category Codes table (F03012A). Multiple records can be entered at one time with different effective dates on the Date Effective Category Codes Revision form. When adding date-effective category code records, the system updates the Eff Used field with N to indicate that the record is not used. The Date Effective Category Code Update program copies the values of the effective category codes record to the customer master category codes in the Customer Master by Line of Business table (F03012) and changes the value of the Eff Used field to Y. The system does not update the new category code value on the customer record until the Date Effective Category Code Update program is ran (R03012A).
When deleting a Date Effective Category Code and running the Date Effective Category Code Update program, the system does not update the category code value to blank. To remove a value previously updated, override the value to blank, and then run the update program. Once an effective date category code is deleted, it no longer exists in the system.
Category Codes that are no longer effective can be purged by running the Purge Date Effective Category Codes program (R03012B).
Note: Each Date Effective Category Code record entered is independent on previous records. Therefore, complete all desired values for system to use for each record. For example, if a value in category code 1 exists, and a new record with a value in category code 2 is added, the value for category code 1 must be re-entered in the new record or the system will update it to blank.
Complex Groups rules prior to 8.9
The number of category codes available for defining customer groups and item groups was four. The number of category codes available for order detail groups was three. The data item for the third Category Code selected can only be 8 characters in length. So, for example, if MCU field was selected as the third Category Code the system would error because the MCU field is 12 characters in length. Therefore, if user would like to use MCU field, it will need to be the first or second Category Code selected.
The category codes from the Address Book were used depending on how the Accounts Receivable Constants were set. As of SAR #5003614 (XE) and SAR # 4979009 (B73.3.2), if Line of Business is turned on in the Accounts Receivable Constants, then Advanced Pricing will use the Category Codes in the Customer Master (F03012). If the Accounts Receivable Constants are set to use World AR or EnterpriseOne AR, then Advanced Pricing will use the Category Codes in the Address Book (F0101). Note: In EnterpriseOne 8.9 and above, Advanced Pricing will always use the Category Codes in the Customer Master (F03012) regardless of the Accounts Receivable Constants setting.
When Line of Business is used, the company of the Header Branch/Plant is used to determine which Customer Master (F03012) record is selected to use for Category Code and Customer Group retrieval.
To verify the Accounts Receivable Constants, go to P0000, click Accounts Receivable Constants. Search and select on Company 00000. Take the FORM exit to Enhanced AR. The World AR, EnterpriseOne AR, and EnterpriseOne AR –Line of Business flags are set here.
Answer1: When using complex groups (item, customer or order detail)blank is not a valid value therefore the error being thrown is valid. See Bug 12470261 : BLANK CAT CODE NOT ALLOWED - SAR: 4338236 which states: Since order detail groups are defined by their category codes, blanks are not valid when setting them up. The complex group UDC (item, customer and order detail) allow for blanks when setting them up, however Pricing does not allow for blank, a value is required when used with adjustments. These fields cannot be blank.
Answer 2: In JD Edwards EnterpriseOne Release XE, the “Work With Adjustment Detail” P4072 application was based on business view V4072A and displayed the following fields from table F4072: Order Detail (SDGR), Sales Detail Value 01 – 03 (SDV1 SDV2, SDV3), Item Grp 01 – 04, Cust Grp 1 – 4.
In Release 9.1 (starting with release 8.9), the application P4072 grid is based on a new business view V4072B, which is a join on 4 tables: F4072 and 3 new tables: Item Key ID Master File (F40941), Customer Key ID Master File (F40942), Order Group Key ID Master File (F40943).
The fields Order Detail (SDGR) and Sales Detail Value 01 – 08 (SDV1 – SDV8) are from table F40943. The fields Item Grp 01 – 10 (IGP1 – IGP10) fields from table F40941. The fields Cust Grp 1 – 10 (CGP1 – CGP10) are from table F40942. The link between the tables is based on the common field OrderGroupKeyID (OGID).
FRAT and RATT fields have been removed from the details of the sales order and no longer can be used to define the groups.