-
Automation to include validation reports based on SPRO configuration and MRP profiles
For SAP migrations, we are auto creating "some" validation rules but not he ones that check SPRO values for Mandatory, optional and suppressed field usage by (for example) Customer and Vendor account group and Material group as well as validating ...4 Unlikely to Implement
-
Value Mapping Legacy Description NOT inserted via autogen rule
When autogen creates the cross reference rules if you have a field set to XREF in MAP, the following rules get built to insert unique values to Value Mapping (example): srANLZ_C1_ECP_Milano_Approved_ANLZ_zPS_PSP_PNR2_xtPRPS010 srANLZ_C1_ECP_Milano...1 Unlikely to Implement
-
Create a st table that does not include all of the columns specified in the Source System Type for that table
Could we have a mechanism to create a st table (st package) that that does not include all of the columns specified in the Source System Type for that table. i.e. only create the st table with reference to the fields that are active in Map, Target...0 Unlikely to Implement