10 Integrating with Oracle Global Order Promising

This chapter contains the following topics:

10.1 Understanding JD Edwards EnterpriseOne Integration with Oracle Global Order Promising

The JD Edwards EnterpriseOne integration with Oracle Global Order Promising (GOP) enables you to source in real time by determining the source of supply and promise date. The user can select the promise date to be either the ship date or the delivery date.

This integration provides organizations with:

  • Sourcing of Branch/Plant and promise dates from the GOP sourcing engine.

  • Flexibility to determine source of supply from the GOP or the EnterpriseOne Sales Order system based on your business requirements, using advanced preferences.

    Note:

    A sales order can have a mix of lines sourced from GOP or the EnterpriseOne Sales Order system.

The sourcing with promise date calculation takes into account the complexity of supply chain factors, which include:

  • Multi-level bill of materials and manufacturing

  • Delivery lead times for internal and external customers

  • Resource and material constraints

  • Supplier constraints

  • Substitute end items

  • Multi-facility sourcing

Note:

Global Order Promising marshals a product from various locations to the single sales order shipping location.

Note:

The EnterpriseOne-GOP integration does not work with the JD Edwards EnterpriseOne Fulfillment Management system.

10.2 Activating the JD Edwards EnterpriseOne Integration with Oracle Global Order Promising

Before you can use the features of the EnterpriseOne-GOP integration, you must activate GOP within the JD Edwards EnterpriseOne system. When you activate the GOP integration, the system enables GOP-specific setup and logic.

10.2.1 Form Used to Activate JD Edwards EnterpriseOne Integration with GOP

Form Name Form ID Navigation Usage
EnterpriseOne System Control - Revisions W99410A Data Relationships (G09415), Activate Data Relationships.

On the Work With EnterpriseOne System Control form, locate data item SY34AGOP.

Select the row and click Select.

On the EnterpriseOne System Control - Revisions form, select Yes to activate the data item. Click the OK button.

Bounce the EnterpriseOne server.

Activate JD Edwards EnterpriseOne integration with Oracle Global Order Promising.

10.2.2 Activating JD Edwards EnterpriseOne Integration with GOP

Access the EnterpriseOne System Control - Revisions form.

When you activate system constant SY34AGOP, the system displays the Ship/Delivery field in the Customer Billing Information program (P03013) on the Billing 2 tab. Use this field to indicate which date or set name the system uses when promising a sales order with Global Order Promising. You can specify the ship date or the delivery date.

Note:

To process sales orders using GOP integration, you must use a version of the Sales Order Entry program (P4210) that is set to process orders in GOP mode. The processing option to specify GOP processing mode is located on the Global Order Promising tab.

10.2.2.1 Setting Up Ship/Delivery Date Codes

Before sourcing, verify that the Ship/Delivery Date codes are set in the UDC 34A/AS table.

To set up/verify UDC values:

  1. Access the Customer Master Billing Information form and select the Billing 2 tab.

  2. In the Ship/Delivery Date field, verify that UDC 34A/AS has these values.

    Ship/Delivery Date

    Enter a value from UDC 34A/AS to indicate which date the system uses when promising a sales order with GOP.

    Valid values are:

    • Blank: Use P34A10 setting

    • 1: Use the ship date

    • 2: Use the delivery date

10.3 Understanding JD Edwards EnterpriseOne Configuration

Two processes must be customized to implement the integration between JD Edwards EnterpriseOne and GOP applications:

  • JD Edwards EnterpriseOne applications including versions, processing options, integration constants, and file definitions

  • Scripts that transfer JD Edwards EnterpriseOne data from the JD Edwards EnterpriseOne server to the GOP server.

    The scripts also perform synchronization and error checking.

To set up the configuration for this integration, see the following chapters in the Oracle Value Chain Planning Integration Base Pack Implementation Guide:

  • Chapter 6, ”Configuring JD Edwards EnterpriseOne.”

  • Chapter 7, ”Configuring JD Edwards EnterpriseOne UBEs.”

10.4 Setting Up Resources

Resources are necessary to set up manufacturing packages. This action enables the system to properly write information to manufacturing packages.

10.4.1 Forms Used to Set Up Resources

Form Name Form ID Navigation Usage
Master Planning Resource Revisions W34A80A Planning & Scheduling (G34A/SCBM/SU), Master Resource Setup.

On the Master Resource Browse form, click Add.

Set up master planning resources.
Routing Master Resource Set Definition W34A180A Daily PDM Process (G3012), Enter/Change Process.

On the Work With Routing Operations form, enter a branch/plant and item number. Click Find.

Select Planning Resources from the Row menu.

Attach work center resources to routing steps.
Routing Master Resource Set Detail Definition W34A190A On the Routing Master Resource Set Definition form, select a record Edit routing master resource set detail information.
Work Center Resource Set Detail Definition W34A170A Periodic Resource / Capacity Planning (G3322), Enter/Change Workcenters.

On the Work With Work Centers form, locate and select a work center. Select Planning Resources from the Row menu.

On the Work Center Resources Set Definition form, select a record and click the Edit Resource button.

Edit work center resources.

10.4.2 Attaching Work Center Resources to Routing Steps

Access the Routing Master Resource Set Definition form.

Note:

Make sure you set the value for UDC 34A/GU to option 6 - Alternate Resources.

10.4.3 Revising Routing Master Resource Set Definition Detail

Access the Routing Master Resource Set Detail Definition form.

10.4.4 Editing Work Center Resources

Access the Work Center Resource Set Detail Definition form.

10.4.5 Setting Processing Options for the VCP Planning BOM Creation Program (R34A1020PB)

Use these processing options to define how the system processes data.

10.4.5.1 Process

1. Type Bill of Material

Specify the type of bill (40/TB) the system adds when you run the VCP Planning BOM Creation program. If you leave this option blank, the system uses code PB (planning BOM) as the default value.

Note:

For Manufacturing XML build, PB (planning BOM) is the only BOM type the system writes to file for configured items.
2. Mandatory Item Planned Percent

Specify the percentage of demand for a specified feature based on projected production. For example, a company might produce 65 percent of its lubricant with high viscosity, and 35% with low viscosity, based on customer demand. If you leave this option blank, the system uses 100 percent as the default value.

The Material Planning system uses this percentage to accurately plan for a process's co-products and by-products.

Enter percentages as whole numbers, for example, enter 5 percent as 5 instead of .05.

3. Optional Item Planned Percent

Specify the percentage of demand for a specified feature based on projected production. For example, a company might produce 65 percent of its lubricant with high viscosity, and 35% with low viscosity, based on customer demand. If you leave this option blank, the system uses 100 percent as the default value.

The Material Planning system uses this percentage to accurately plan for a process's co-products and by-products.

Enter percentages as whole numbers, for example, enter 5 percent as 5 instead of .05.

4. Purge Selected Records Before Updating in F3002

Specify whether the system clears selected Bill of Material Master File (F3002) records before adding new records into the table. Values are:

Blank or Y: Clear selected Bill of Material Master File records before updating all new components to BOM.

N: Append the new components to any existing BOM. This process does not change any component records that exist in the table.

5. P3002 Version to use

Specify which version of the Bill of Materials Revisions program (P3002) the system uses to create F3002 records. If you leave this option blank, the system uses version ZJDE0001.

10.5 Setting Up Items for GOP Processing

To process an item for GOP processing, you must activate the Constraints Flag option in the item/branch plant record. Activating this flag enables the JD Edwards EnterpriseOne system to include the item in the VCP process.

Note:

You can run the Update GOP Constraints Flag batch program (R41910) to update the constraints flag for multiple items based on the data selection criterion specified during report generation.

10.5.1 Form Used to Setup Items for GOP Processing

Form Name Form ID Navigation Usage
Additional System Info W41026D Inventory Master/Transactions (G4111), Item Branch/Plant

On the Work With Item Branch form, locate and select an item in a branch/plant.

Select Addl System Info from the Row Menu.

On the Additional System Info form, access the Supply Chain Planning tab.

Set up items for GOP processing.

10.5.2 Setting Up an Item for GOP Processing

Access the Additional System Info form.

Constraints Flag

Specify whether the system includes the item in VCP. Values are:

0: Do not include item in VCP

1: Include item in VCP

Sellable Item

Select this option to identify an item as sellable. Its usage is for VCP integrations exclusively.

Check ATP (Available to Promise)

Specify whether the GOP system performs an ATP check on the item during the real-time promise. This works with the Constraints flag. In order for the system to send an item to GOP, you must activate the ATP check flag. This allows GOP to perform an ATP check based on the ATP rule defined below.

ATP Components

This works with the ATP check option, which specifies the type of ATP check the GOP system performs on the item bill of materials to determine the promised delivery date. Values are:

M: Materials only

MR: Material and resource

N: None

R: Resource only

Note:

For a configured item, set the ATP components to N for all of its nonconfigured components.
ATO Forecast Control

Use this field to specify forecasting that the Demantra integration uses. Values are:

Blank: None

1: Consume

2: Consume and derive

ATP Rule Name

Specify the ATP rule the system uses to promise the order. The ATP rules are stored in the ATP Rules table (F34A210).

10.5.3 Setting Up Processing Options for Update GOP Constraints Flag Using UBE - R41910 (Release 9.2 Update)

For an item to be promisable by GOP, you must set the constraints flag for the item in the Item Branch File table (F4102). You can run the Update GOP Constraints Flag batch program (R41910) to update the constraints flag for multiple items based on the data selection criterion specified during report generation. The mass update of the constraints flag makes setup and modifications easier.

10.5.3.1 Update

Proof or Final Mode

Specify whether the system runs in proof or final mode. You must use the version that is specific to the company's update process, and for any version you must indicate whether the system uses proof or final mode. Values are:

Blank: Run in proof mode

The system generates a report but does not update the respective tables.

1: Run in final mode

The system generates a report and updates the respective tables.

Constraints Flag

Select a constraints flag value from UDC table 42/AC. Values are:

Blank: No Setup

0: Item Not Included in APS

1: Item Included in APS

Display Output

Specify whether the report should display all records, only updated records, or only error records. Values are:

Blank: Display all the records

1: Display only updated records

2: Display only error records

Note:

If the R41910 report displays any error, check the JD Edwards EnterpriseOne Update Center for details.

10.5.4 Configured Items

The system promises the configured order if the parent item is promisable. You must set the constraints flag for the configured item in the item branch. The configured item is promisable and not dependent upon you setting the Check ATP option. When the order entry program receives a different promised date from GOP, the system updates the new promised date to the configured parent line only. The system does not update component lines with the new promised date. The component lines retain the original promised date.

10.6 Setting Up Available to Promise (ATP) Rules

To implement ATP, you begin by defining your ATP rules in the GOP system. ATP rules let you tailor the ATP calculation to suit your business needs. Each rule is a combination of ATP computation options, time fence options, and supply and demand sources to use during an ATP inquiry.

You can define multiple ATP rules to reflect the specific needs of your organization, and then use different rules to calculate availability for different items or groups of items. Each time you run an ATP check, the rule determines how existing supply and demand are matched.

10.6.1 Form Used to Set Up ATP Rules

Form Name Form ID Navigation Usage
ATP Rules Setup W34A210B On the ATP Rules Inquiry form, click Add. Set up ATP Rules

10.6.2 Setting Up ATP Rules

Access the ATP Rules Setup form.

Name

Enter the name and description of the ATP rule.

ATP by Demand Class

Select the check box to specify that the system includes the demand by class in the ATP computation.

(Past Due Days) Demand

The system does not consider the demand before the specified number of days in ATP computation

(Past Due Days) Supply

The system does not consider the supply before the specified number of days in ATP computation

(Demand Sources) Sales Orders

Select the check box to specify that the system includes the demand for sales orders in the ATP computation.

(Demand Sources) Internal Orders

Select the check box to specify that the system includes the demand for internal orders in the ATP computation.

(Demand Sources) Discrete WIP

Select the check box to specify that the system includes the demand for discrete WIP jobs in the ATP computation.

(Infinite Suppy) Options

Enter a source code for infinite supply time fence. Values are:

Blank: None

1: Cumulative total lead time

2: Cumulative manufacturing lead time

3: Total lead time

4: User-defined time fence

(Infinite Supply) Days

Specify infinite supply time fence days only if the infinite supply fence code is user- defined.

(Aggregate Order Promising Time Fence) Options

Enter a source code for aggregate order promising time fence. Values are:

Blank

1: None

2: Demand Time Fence

3: Planning Time Fence

4: User-defined

(Aggregate Order Promising Time Fence) Days

Specify the aggregate time fence days only if the aggregate order promising time fence options is user-defined.

(Supply Sources) Purchase Orders

Select the check box to specify that the system includes the supply from purchase orders in the ATP computation.

(Supply Sources) On-Hand Available

Select the check box to specify that the system includes the supply from on-hand inventory in the ATP computation.

(Supply Sources) Discrete WIP

Select the check box to specify that the system includes the supply from discrete WIP receipts in the ATP computation.

(Supply Sources) Internal Reqs

Select the check box to specify that the system includes the supply from internal requisitions in the ATP computation.

(Supply Sources) Intransit Shipments

Select the check box to specify that the system includes the supply from inter organizational transfers in the ATP computation.

10.7 Configuring JD Edwards EnterpriseOne for Branch/Plant Sourcing from GOP (Release 9.2 Update)

You can configure EnterpriseOne to determine whether to source Branch/Plant from the JD Edward EnterpriseOne system or the GOP system. The system sources promise dates from the GOP system in both instances.

  • To source Branch/Plant from the GOP system, configure the system using advanced preferences.

  • To source Branch/Plant from the JD Edwards EnterpriseOne system, you do not need to set up advanced preferences.

10.7.1 Understanding JD Edwards EnterpriseOne Configuration for Branch/Plant Sourcing

To source Branch/Plant from GOP, set up advanced preferences in the JD Edwards EnterpriseOne system.

For example, the configuration can be defined for an item, item group, customer, customer group, category codes, business unit, any combination of these categories, or for all items and customers.

This table describes the behavior of the system when GOP processing is enabled.

Advanced Preference Set (Yes/No) Source Branch/Plant From
Yes GOP
No JD Edwards EnterpriseOne

10.8 Sourcing from the Global Order Promising (GOP) System (Release 9.2 Update)

You can source the Branch/Plant along with the promise dates for line items. The Global Order Promising system processes the sales order requests based on the ATP rules.

The EnterpriseOne-GOP integration enables you to override the Branch/Plant value. When you override the Branch/Plant value for a sales order line item, the GOP system accepts the overridden Branch/Plant and suggests the promise date for that line item.

10.8.1 Prerequisites

  • Run the Preference Values Definition Update program (R40711S) to correctly populate the Preference Values Definition table (F40711).

  • Before setting up advanced preferences for GOP sourcing, verify that the advanced preference type code 47 is defined in UDC 40/AP for GOP Preference.

  • Before sourcing, verify that the Ship/Deliver Dates codes are set up in the UDC 34A/AS table. Refer to Section 10.2.2.1, "Setting Up Ship/Delivery Date Codes" for more information.

10.8.2 Forms Used to Set Up Advanced Preferences for GOP Sourcing

Form Name Form ID Navigation Usage
Preference Definition Revisions W4071A Advanced Preferences (G40311), Advanced Preferences Name Revisions

Click Add on the Work with Preference Types form.

Set up preference definitions.
Preference Schedule Revisions W4070C Advanced Preferences (G40311), Advanced Preferences Schedule Revisions

Click Add on the Work with Preference Schedules form.

Set up preference schedules.
Preference Detail Revisions W4072A Advanced Preferences (G40311), Advanced Preferences Detail Revisions

Search for a Preference Name and click Add on the Work with Preference Detail form.

Select the appropriate combination and click Select on the Preference Hierarchy Selection form.

Set up preference details.
Preference Values Revisions W4072C Select a row and select Pref Details from the Row menu. Set up preference detail values.

10.8.3 Setting Up Advanced Preferences for GOP Sourcing

Note:

Set up Advance Preferences only if you want to source the Branch/Plant from GOP.

See Setting Up Advanced Preferences.

To configure advanced preferences:

  1. Run the Preference Values Definition (F40711) Update report (R40711S) to insert the preference details into the Preference Values Definition table (F40711).

    This is a one-time setup before configuring the advance preferences.

  2. Set up a new preference for GOP in the Preference Definition Revisions form.

  3. Set up preference details for the GOP preference that you created, using the Preference Detail Revisions form.

    Advanced Preference Type - Verify that the value 47 - GOP Preference exists in UDC 40/AP. This value specifies how the system processes an advanced preference adjustment.

  4. Set up preference detail values using the Preference Values Revisions form.

  5. Define a schedule for the advance preference using the Preference Schedule Revisions form.

  6. Attach the GOP schedule that you created to the processing option of the sales order version (P4210).

    1. Enter P4210 in the Interactive Versions field and click Find.

    2. Select the program version (GOP version), and then select Processing Options from the Row menu.

    3. Select 5 - Commitment from the drop-down menu and set 1. Activate Availability Checking as Blank or 2 so that the system does not back order the Order line.

    4. Select 10-Preference from the drop-down menu.

    5. Set the Preference Profile Processing to 1 and enter the schedule that you defined for GOP sourcing in the Override Schedule for Advanced Preferences field and then click OK.

10.8.4 Forms Used to Source from GOP

Form Name Form ID Navigation Usage
Customer Service Inquiry W4210E Sales Order Processing (G4211), Sales Order Detail Review and select sales order detail records, or access forms to add a new sales order.
Sales Order Header W4210G Click Add on the Work With Sales Order Headers form to add a new sales order.

Select a record on the Work With Sales Order Headers form, and click Select to revise an existing sales order.

Enter sales order header information.
Sales Order Detail Revisions W4210A Click OK on the Sales Order Header form. Enter sales order item information.

Enter default line information.

Review secondary unit of measure and quantity information for the appropriate items.

Override the default price and cost, or change the values to zero.

Global Order Promising Results W4210GOPB Select Order Promising > GLBL Order Promising from the Form menu on the Sales Order Detail Revisions form. Review the GOP order promising results.
Order Acceptance W42232A Click OK on the Sales Order Detail Revisions form. Click the appropriate button to place or revise the order.

10.8.5 Sourcing Branch/Plant with Promise Dates for Sales order Lines

You use the Sales Order Entry program (P4210 or P42101) to process sales order lines in the GOP mode.

To source the Branch/Plant for the sales order lines:

  1. Create a new sales order (P4210)
    or access the Sales Order Entry program (P42101).

  2. Set up the GOP flags in the Global Order Promising Overrides tab of the Sales Order Header form and click OK.

    The system allows overrides for the following flags defaulted from the customer master:

    • GOP Partial Order Shipments Allowed

    • GOP Partial Shipments Allowed

    • GOP Backorders Allowed

    • GOP Substitutes Allowed

  3. Add the line items for the sales order in the Sales Order Details Revisions form.

  4. Select Order Promising > GLBL Order Promising option from the Form menu. The Review Global Order Promising Results form displays the GOP promise results for all the line items eligible for GOP promise.

  5. Click OK to accept the GOP promise results.

    The system updates the Sales Order Detail Revisions form with the sourcing results from the GOP system.

10.8.6 Sourcing Branch/Plant for Kit Items

You can source the Branch/Plant along with the promise dates for kit items from the GOP system. The system considers a kit item to be a ship set and provides the same promise dates and Branch/Plant value for all components in the kit. The kit components are all promised from the same Branch/Plant.

To source the Branch/Plant for kit items from GOP:

  1. Create an order for a parent kit item from the Sales Order Entry program (P4210 or P42101).

  2. Tab down. The system displays the Kit Selection form.

  3. If required, select the optional kit items.

  4. Verify the kit components, and click OK.

  5. Select Order Promising > GLBL Order Promising option from the Form menu. The Review Global Order Promising Results form displays the GOP promise results for the kit components.

  6. Click OK to accept the GOP promise results.

    The system synchronizes the updates to the sales order lines in the Sales Order Detail Revisions form.

10.8.7 Sourcing Branch/Plant for Configuration Items

You can source the Branch/Plant for configuration items only from the JD Edwards EnterpriseOne system. The system does not support sourcing Branch/Plant for configuration items from GOP.

When you source for a configuration item, the GOP system accepts the source Branch/Plant suggested by the JD Edwards EnterpriseOne system and processes the promise date for the configuration item.

10.8.8 Reviewing Global Order Promising Results

The Review Global Order Promise Results program (P4210GOP) enables you to review the order promising results for an order. The system activates the P4210GOP program when you set the Sales Order Entry program (P4210) to process sales orders in global order promising mode. You can also access the P4210GOP program from the Sales Order Entry program (P42101). When you access the P4210GOP program, the system performs a real time promise request and displays the results. After the system displays the results, you can filter order lines based on lines with errors, lines with changes, or lines with no changes.

10.9 Setting Up GOP Business Services

This section provides an overview of web services callout and discusses how to:

  • Configure the GOP processor.

  • Set up soft coding templates.

  • Set up web service soft coding records.

10.9.1 Understanding Web Services (WSC) Callout

The Web Services Callout integration uses the GOP JAXRPC Processor (JC34A010) or the GOP JAXWS Processor (JC34A020) business services to call the GOP web service. The business service retrieves order promise dates from the Oracle Global Order Promising system. The service supports order promise dates for backorders, substitute orders, and partial orders.

10.9.2 Configuring the GOP Processor

The GOP functionality runs on any of the supported application servers. The type of business service build that you are currently using or that you wish to use with this service determines which of the two business service objects JC34A010 or JC34A020 you must configure. The following is a table that assists you with your decision. The fourth column in the table indicates the value that you need to add to the Oracle Global Order Promising system level business server property (JC34A0000_APP_SERVER).

Server Build Type Business Service Value in J34A0000_APP_SERVER
WebLogic Server (WLS) JAX-WS with JDeveloper 11g (Tools 9.1.2 or later) JC34A020 JAXWS
WebLogic Server (WLS) JAX-RPC with JDeveloper 11g JC34A010 JAXRPC
Websphere Application Server (WAS) JAX-WS with JD Developer 11g (Tools 9.1.2 or later) JC34A020 JAXWS

10.9.2.1 GOP JAXRPC Processor Business Service (JC34A010)

The GOP JAXRPC Processor business service (JC34A010) runs on the Oracle WebLogic Server (WLS) platform and reads the data stored in these tables:

  • Customer Master by Line of Business (F03012)

  • APS Integration Constants (F34A10)

  • Numetrix Integration File Definition (F34A11)

  • Work Center Resource Table (F34A110)

  • ATP Rules (F34A210)

  • Order Status Definition Table (F34A30)

  • Item Master (F4101)

  • Item Branch File (F4102)

  • Sales Order Detail File (F4211)

  • Sales Order Detail File - Tag File (F49211)

  • Routing Entries (F4950)

The E1 Enterprise server collects the data required for determining promised delivery date from the JD Edwards EnterpriseOne tables and then calls the JC34A010 business service. The JC34A010 business service makes the necessary calls to the GOP web methods and returns the promised dates received from GOP to the E1 Enterprise server.

Before you use JC34A010, you can set business service properties, which the system uses to process user authentication information. You must set up these properties before you can use the business service. This table describes each of the properties associated with this business service:

Group Key Description Value
JC34A010 JC34A010 Used this business service property to indicate the value of the URL used to access the GOP web service. Provided by GOP.

10.9.2.2 GOP JAXWS Processor Business Service (JC490020)

The GOP JAXWS Processor business service (JC34A020) runs on the Oracle WebLogic Server (WLS) platform or the Web Application Server (WAS) platform, and reads the data stored in these tables:

  • Customer Master by Line of Business (F03012)

  • APS Integration Constants (F34A10)

  • Numetrix Integration File Definition (F34A11)

  • Work Center Resource Table (F34A110)

  • ATP Rules (F34A210)

  • Order Status Definition Table (F34A30)

  • Item Master (F4101)

  • Item Branch File (F4102)

  • Sales Order Detail File (F4211)

  • Sales Order Detail File - Tag File (F49211)

  • Routing Entries (F4950)

The E1 Enterprise server collects the data required for determining promised delivery date from the JD Edwards EnterpriseOne tables, and then calls the JC34A020 business service. The JC34A020 business service makes the necessary calls to the GOP web methods and returns the promised dates received from GOP to the E1 Enterprise server.

Before you use JC34A020, you can set business service properties, which the system uses to process user authentication information. You must set up these properties before you can use the business service. This table describes each of the properties associated with this business service:

Group Key Description Value
JC34A020 JC34A020 Used this business service property to indicate the value of the URL used to access the GOP web service. Provided by GOP.

10.9.3 Setting Up Soft Coding Templates

To update soft coding templates:

  1. Access the Add Soft Coding Template form.

    Form Name Form ID Navigation
    Update Soft Coding Template W953000C Soft Coding Administration menu (GH90906).

    Select Soft Coding Template (P953000).

    On the Work with Soft Coding Templates form, locate and select a soft coding template.

    Select the template name.


  2. On the Update Soft Coding Template form, complete the following field:

    Value

    The template value or soft coding value is an XML string. The XML string can contain an element with the following dynamic variables:

    • $e1user

    • $e1environment

    • $e1role

    • $ps_token

During run-time, actual values replace the dynamic variable values. This table lists the soft coding key and the XML string value for each respective soft coding key:

Soft Coding Key XML String Value
JC34A010 <scwls>

<endpoint>Enter endpoint URL here</endpoint>

<username>Enter user name</username>

<password>_||_password_||_</password>

<respname>Enter responsibility name</respname>

<respapplname>Enter responsibility application name </respapplname>

<securitygroupname>Enter security group name here </securitygroupname>

<language>Enter language here</language>

</scwls>

JC34A020 <scwls>

<endpoint>Enter endpoint URL here</endpoint>

<username>Enter user name</username>

<password>_||_password_||_</password>

<respname>Enter responsibility name</respname>

<respapplname>Enter responsibility application name </respapplname>

<securitygroupname>Enter security group name here </securitygroupname>

<language>Enter language here</language>

</scwls>


10.9.4 Setting Up Web Service Soft Coding Records

To update soft coding templates:

  1. Access the Update Web Service Soft Coding Record form.

    Form Name Form ID Navigation
    Update Web Service Soft Coding Record W954000B Soft Coding Administration menu (GH90906).

    Select Soft Coding Records (P954000).

    On the Work with Web Service Soft Coding Records form, locate and select a soft coding record.


  2. On the Update Web Service Soft Coding Record form, complete the following fields:

    User / Role

    Enter a profile that you use to classify users into groups for system security purposes. You use group profiles to give the members of a group access to specific programs. Rules for creating a profile for a user class or group include:

    • The name of the user class or group must begin with an asterisk (*) so that it does not conflict with any system profiles.

    • The User Class/Group field must be blank when you enter a new group profile.

    Environment Name

    Enter an environment name. For JD Edwards EnterpriseOne installed applications, the environment name is also called the plan name, which you use to uniquely identify an upgrade environment for install and reinstall.

    For JD Edwards EnterpriseOne environment or version applications, this is the path code that identifies the location of the application or version specification data.

    Soft Coding Value

    The template value or soft coding value is an XML string. The XML string can contain an element with the following dynamic variables:

    • $e1user

    • $e1environment

    • $e1role

    • $ps_token

During run-time, actual values replace the dynamic variable values.