Customizing IS Document Types for Existing Standard RosettaNet PIPs
You can customize an IS document type for an existing standard RosettaNet PIP. You may want to do this, for example, if the PIP has fields that your trading partners are unable to populate, or are not needed for your business needs. There are two options for altering an IS document type:
Change unnecessary fields to make them optional.
Advantage: Allows documents for that PIP to pass validation.
Disadvantage: Affects every trading partner exchanging this PIP with you.
Isolate changes to the IS document type for a specific trading partner only.
Advantage: Localizes changes for one trading partner and one particular PIP only.
Disadvantage: Creates an additional IS document type to maintain.
To isolate changes for an IS document type, follow these steps:
1. Create a folder in the WmRNPips package under wm.b2b.rn.rec.PIPs and name it <your customized PIP structure>.
2. Enter the new location as the value for the NSFolder parameter in the TPA for that PIP.