System Unavailable at This Time Try Again Later V01

Utilise a spider web service to get costs from Oracle Fusion Costing, then mark it up or down according to rules on the price list.

Oracle Fusion Pricing comes predefined to support toll plus pricing through costs that you set up on the Manage Cost Lists page in the Pricing Assistants work area. Instead, y'all can get item cost from an external system that resides outside of Pricing, such as Oracle Fusion Costing.

You lot modify a pricing algorithm so it calls a SOAP or REST API web service. You utilize Oracle Integration Cloud to route the call.

This topic assumes.

• You already set up Pricing. For details, see the Roadmap to Managing Oracle Fusion Pricing topic.

• Customer Reckoner Service and Rentals is function of the Corporate Segment pricing segment and the Corporate Pricing Strategy.

• You get costs from the costing service co-ordinate to Inventory Organization.

The spider web service is secure, and so use a secure tool, such as Lather UI, to send and receive your payloads.

This topic includes case values. You might use different values, depending on your business organization requirements.

Summary of the Set

A. Test the costing service.

B. Set up up your integration.

C. Test the soap service.

D. Set up the connector in Oracle Fusion.

E. Edit the service mapping.

F. Troubleshoot.

A. Test the Costing Service

Telephone call the costing SOAP web service to make sure it works.

1. Create an input test payload.

   Hither's an case input payload yous can use.

                   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/scm/costing/itemCosts/itemCostServiceV2/types/" xmlns:detail="http://xmlns.oracle.com/apps/scm/costing/itemCosts/itemCostServiceV2/"> <soapenv:Header/>   <soapenv:Body>     <typ:retrieveItemCost>     <!--Zero or more than repetitions:-->       <typ:costparams>         <detail:ItemId>149</item:ItemId>         <item:InventoryOrganizationId>204</item:InventoryOrganizationId>         <item:UnitOfMeasure>Ea</item:UnitOfMeasure>       </typ:costparams>       <typ:costparams>         <item:ItemId>151</item:ItemId>         <detail:InventoryOrganizationId>204</item:InventoryOrganizationId>         <item:UnitOfMeasure>Ea</item:UnitOfMeasure>       </typ:costparams>     </typ:retrieveItemCost>   </soapenv:Body> </soapenv:Envelope>              

2. Send your input payload to the costing service.

   Use the WSDL URL for your example of Oracle Fusion Pricing. Hither'due south an example.

   http://myServer.myCompany.com:10663/fscmService/ItemCostServiceV2?WSDL

3. Examine the response payload that the costing service sends to yous.

   Here's an example of the response payload.

                   <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:typ="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/types/">   <env:Header>     <wsa:Action>http://xmlns.oracle.com/apps/scm/costing/itemCosts/service//ItemCostService/retrieveItemCostResponse</wsa:Action>     <wsa:MessageID>urn:uuid:1b2f8967-12ef-4740-8ba0-1b02b85d10c4</wsa:MessageID>   </env:Header>   <env:Body>     <ns0:retrieveItemCostResponse xmlns:ns0="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/types/">       <ns2:result xsi:blazon="ns1:ItemCostOutputResult" xmlns:ns2="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/types/" xmlns:ns1="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/" xmlns:tns="http://xmlns.oracle.com/adf/svc/errors/" xmlns:ns0="http://xmlns.oracle.com/adf/svc/types/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">         <ns1:Value>           <ns1:ItemCost>53.77873553551955</ns1:ItemCost>           <ns1:CurrencyCode>USD</ns1:CurrencyCode>           <ns1:UOMCode>Ea</ns1:UOMCode>           <ns1:ErrorFlag>fake</ns1:ErrorFlag>           <ns1:ItemID>149</ns1:ItemID>           <ns1:InvOrgID>204</ns1:InvOrgID>           <ns1:SubInvCode xsi:nix="true"/>           <ns1:Locator xsi:nil="truthful"/>           <ns1:LotNum xsi:nil="true"/>           <ns1:SerialNum xsi:zip="true"/>           <ns1:Course xsi:nil="true"/>           <ns1:KindOfCost xsi:zilch="true"/>           <ns1:KindOfCostDetail xsi:nil="true"/>           <ns1:RefDate>2019-07-15T00:00:00.0Z</ns1:RefDate>           <ns1:ItemNumber xsi:goose egg="true"/>           <ns1:InvOrgCode xsi:naught="true"/>           <ns1:UnitOfMeasure xsi:nothing="true"/>         </ns1:Value>         <ns1:Value>           <ns1:ItemCost>-i.0</ns1:ItemCost>           <ns1:CurrencyCode xsi:nil="true"/>           <ns1:UOMCode>Ea</ns1:UOMCode>           <ns1:ErrorFlag>truthful</ns1:ErrorFlag>           <ns1:ItemID>151</ns1:ItemID>           <ns1:InvOrgID>204</ns1:InvOrgID>           <ns1:SubInvCode xsi:nil="true"/>           <ns1:Locator xsi:nix="true"/>           <ns1:LotNum xsi:nix="truthful"/>           <ns1:SerialNum xsi:nil="true"/>           <ns1:Grade xsi:naught="true"/>           <ns1:KindOfCost xsi:nothing="true"/>           <ns1:KindOfCostDetail xsi:nil="truthful"/>           <ns1:RefDate xsi:zip="true"/>           <ns1:ItemNumber xsi:nil="truthful"/>           <ns1:InvOrgCode xsi:nada="true"/>           <ns1:UnitOfMeasure xsi:nothing="true"/>         </ns1:Value>       </ns2:issue>     </ns0:retrieveItemCostResponse>   </env:Body> </env:Envelope>              

4. Verify the response.

   • Make sure the value nether the ItemCost is correct and that its in the right currency.

   • Make sure each instance of ErrorFlag in the response is false.

B. Gear up Up Your Integration

Use Integration Cloud Service to route your call from your pricing algorithm to the costing service.

Summary of the Set

1. Create WSDL.

2. Create your source connector.

3. Create your target connector.

4. Import a predefined integration.

For details nearly how to use Integration Deject Service, including the URL y'all apply when you sign in, see the Starting Oracle Integration Cloud Service topic on Oracle Help Center.

Create WSDL

Copy this lawmaking into a text editor, such as Notepad ++, and then save it to your local computer with file name ItemCostService.wsdl.

            <?xml version="1.0" encoding="UTF-viii" ?>  <!-- This is an interface WSDL that y'all tin can use to configure a connection in Integration Cloud Service. It's a proxy for the PriceRequestValidation service. This WSDL contains only XSD definitions, Soap letters, and bindings. It doesn't include services for port operations. This WSDL matches 1 of the context consumers that the integration uses for payload exchanges. -->  <wsdl:definitions name="ItemCostService"   targetNamespace="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/"   xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"   xmlns:errors="http://xmlns.oracle.com/adf/svc/errors/"   xmlns:tns="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/"   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"   xmlns:lather="http://schemas.xmlsoap.org/wsdl/soap/"   xmlns:types="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/types/">  <wsdl:types>   <xsd:schema elementFormDefault="qualified"     targetNamespace="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/"     sdoJava:package="oracle.apps.scm.costing.itemCosts.service"     xmlns:sdoJava="commonj.sdo/java"     xmlns="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/"     xmlns:xsd="http://www.w3.org/2001/XMLSchema"></xsd:schema>   <xsd:schema elementFormDefault="qualified"     targetNamespace="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/types/"     xmlns:ns0="http://xmlns.oracle.com/adf/svc/errors/"     xmlns="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/types/"     xmlns:tns="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/types/"     xmlns:xsd="http://www.w3.org/2001/XMLSchema">   <xsd:element name="retrieveItemCost">     <xsd:complexType>       <xsd:sequence>        <xsd:element name="CostParams" type="ItemCostInput"/>       </xsd:sequence>     </xsd:complexType>   </xsd:chemical element>    <xsd:complexType proper name="ItemCostInput">      <xsd:sequence>        <xsd:element minOccurs="0" name="ItemID" nillable="truthful" blazon="xsd:long"/>        <xsd:element minOccurs="0" name="InvOrgID" nillable="true" type="xsd:long"/>        <xsd:element minOccurs="0" proper name="UnitOfMeasureCode" nillable="true" type="xsd:cord"/>      </xsd:sequence>    </xsd:complexType>        <xsd:chemical element name="retrieveItemCostResponse">      <xsd:complexType>         <xsd:sequence>        <xsd:chemical element name="Result" type="ItemCostOutputResult"/>      </xsd:sequence>    </xsd:complexType>    </xsd:element>        <xsd:complexType name="ItemCostOutputResult">      <xsd:sequence>      <xsd:element maxOccurs="unbounded" minOccurs="0" proper name="Value" type="ItemCostOutput"/>     </xsd:sequence>    </xsd:complexType>        <xsd:complexType name="ItemCostOutput">      <xsd:sequence>        <xsd:chemical element minOccurs="0" name="ItemCost" nillable="true" blazon="xsd:double"/>        <xsd:element minOccurs="0" proper name="CurrencyCode" nillable="truthful" type="xsd:string"/>        <xsd:chemical element minOccurs="0" proper name="UnitOfMeasureCode" nillable="true" type="xsd:cord"/>        <xsd:element minOccurs="0" proper noun="ErrorFlag" nillable="true" type="xsd:boolean"/>        <xsd:element minOccurs="0" name="ItemID" nillable="true" blazon="xsd:long"/>        <xsd:element minOccurs="0" name="InvOrgID" nillable="true" type="xsd:long"/>      </xsd:sequence>     </xsd:complexType>   </xsd:schema>    <schema elementFormDefault="qualified"     targetNamespace="http://xmlns.oracle.com/adf/svc/errors/"     sdoJava:package="oracle.jbo.service.errors"     xmlns:sdoJava="commonj.sdo/java"     xmlns:tns="http://xmlns.oracle.com/adf/svc/errors/"     xmlns="http://www.w3.org/2001/XMLSchema">    <element name="ServiceErrorMessage" blazon="tns:ServiceErrorMessage"/>    <complexType name="ServiceMessage">      <sequence>       <chemical element maxOccurs="1" minOccurs="0" name="code" type="cord"/>       <element maxOccurs="one" minOccurs="0" proper name="message" type="cord"/>       <chemical element maxOccurs="1" minOccurs="0" name="severity" blazon="cord"/>       <element maxOccurs="unbounded" minOccurs="0" proper noun="particular"        blazon="tns:ServiceMessage"/>      </sequence>    </complexType>    <complexType proper name="ServiceErrorMessage">     <complexContent>      <extension base="tns:ServiceMessage">       <sequence>        <element maxOccurs="1" minOccurs="0" proper name="sdoObject" type="anyType"/>        <element maxOccurs="ane" minOccurs="0" name="exceptionClassName"                 type="string"/>       </sequence>      </extension>     </complexContent>    </complexType>   </schema>  </wsdl:types>    <wsdl:message proper name="ServiceException">   <wsdl:part name="ServiceErrorMessage" element="errors:ServiceErrorMessage"/>  </wsdl:message>    <wsdl:message name="ItemCostService_retrieveItemCost">   <wsdl:role proper name="parameters" chemical element="types:retrieveItemCost"/>  </wsdl:message>   <wsdl:message name="ItemCostService_retrieveItemCostResponse">   <wsdl:part proper name="parameters" element="types:retrieveItemCostResponse"/>  </wsdl:message>     <wsdl:portType proper noun="ItemCostService">   <wsdl:documentation/>   <wsdl:operation proper name="retrieveItemCost">    <wsdl:input message="tns:ItemCostService_retrieveItemCost"/>    <wsdl:output message="tns:ItemCostService_retrieveItemCostResponse"/>    <wsdl:error proper noun="ServiceException" bulletin="tns:ServiceException"/>   </wsdl:performance>  </wsdl:portType>  <wsdl:binding proper noun="ItemCostServiceSoapHttp"                type="tns:ItemCostService">   <lather:binding style="document"                 transport="http://schemas.xmlsoap.org/soap/http"/>   <wsdl:operation name="retrieveItemCost">    <soap:operation soapAction="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/retrieveItemCost"/>    <wsdl:input>     <soap:body use="literal"/>    </wsdl:input>    <wsdl:output>     <soap:body utilize="literal"/>    </wsdl:output>    <wsdl:mistake proper noun="ServiceException">     <soap:fault name="ServiceException" use="literal"/>    </wsdl:fault>   </wsdl:operation>  </wsdl:bounden> </wsdl:definitions>          

Create Your Source Connector

1. Sign into Integration Deject Service.

2. On the Welcome page, under Starting time Here, click Connections.

3. On the Connections page, click Create.

4. On the Create Connection - Select Adapter dialog, select SOAP.

   Yous tin also select REST, only for this case, nosotros use Soap.

5. In the Create New Connection dialog, set values, then click Create.

   Attribute	Value
   Name	Enter any text. For this example, enter Connect to Cost Source.
   Identifier	CONNECT_TO_COST_SOURCE
   Role	Trigger and Invoke
   Description	Connect to the source we use when pricing items outside of Pricing Assistants.

6. On the Connect to Price Source page, click Configure Connectivity.

7. In the Connectedness Properties dialog, set values, then click OK.

   Connection Holding	Value
   WSDL URL	ItemCostService.wsdl Upload the WSDL you saved to your local computer earlier in this procedure.
   Target Server's TLS Version	TLSv1.one
   Suppress Insertion of Timestamp Into the Request	No
   Ignore Timestamp in the Response Message	Y
   Enable 2 Way SSL for Outbound Connections	Empty
   Identify Keystore Alias Name	Empty

8. Click Configure Security, prepare the value, and then click OK.

   Attribute	Value
   Security Policy	No Security Policy

9. At the top of the page, click Save.

10. Click Test > Validate and Exam, confirm that your integration displays a message at the top of the page.

    Connectedness Connect to Cost Source was tested successfully.

11. Click Close > Close.

Create Your Target Connector

1. On the Connections page, click Create.

2. On the Create Connexion - Select Adapter dialog, select SOAP.

3. In the Create New Connection dialog, set values, then click Create.

   Attribute	Value
   Name	Enter whatsoever text. For this example, enter Connect to Cost Target.
   Identifier	CONNECT_TO_COST_TARGET
   Office	Trigger and Invoke
   Description	Connect to the target we utilise when pricing items exterior of Pricing Assistants.

4. On the Connect to Cost Target page, click Configure Connectivity.

5. In the Connection Properties dialog, set values, then click OK.

   Connection Belongings	Value
   WSDL URL	http://myServer.myCompany.com:10663/fscmService/ItemCostServiceV2?WSDL
   Target Server's TLS Version	TLSv1.1
   Suppress Insertion of Timestamp Into the Request	No
   Ignore Timestamp in the Response Message	Y
   Enable 2 Way SSL for Outbound Connections	Empty
   Place Keystore Alias Proper noun	Empty

6. Click Configure Security, set values, then click OK.

   Attribute	Value
   Security Policy	Username Countersign Token
   Username	Enter the user you utilise when you lot administer Oracle Fusion Pricing.
   Password	Enter the password you lot employ when yous administrate Oracle Fusion Pricing.

7. At the elevation of the folio, click Salvage.

8. Click Test > Validate and Test, confirm that your integration displays a message at the pinnacle of the page.

   Connection Connect to Price Source was tested successfully.

9. Click Shut > Shut.

1. Go to Technical Reference for Oracle Fusion Pricing (Doc ID 2248583.1) on My Oracle Back up, so download the Files That Back up Pricing Examples attachment to your laptop.

   The attachment contains a file named INTEG_FUSIO_PRICI_WITH_EXTER_SYS_01.00.0000.iar. Relieve this file to a folder on your laptop.

2. Become to Integration Deject Service.

3. On the Welcome page, click the Integrations icon.

4. On the Integrations page, click Import.

5. In the Import Integration dialog, browse to the .iar file you lot downloaded, and then click Open.

6. Click Import.

7. On the Integrations folio, click Integrate Fusion Pricing with External Organization, which is the integration you just imported.

8. Examine the integration.

   • Notice that the integration connects the source to the target.

     

     Some of the text might exist difficult to read in this screen impress. Here'southward the aforementioned detail merely in a tabular array.

     Attribute	Value
     Operation	Performance	Direction
     retreiveItemCost	retreiveItemCost	Toward target
     retreiveItemCostResponse	retreiveItemCostResponse	Toward source
     Fault	Mistake	Toward source

   • Click the Request Mapping icon, and so discover the attributes that the integration maps from source to target.

     

     For case.

     Aspect in Source	Attribute in Target
     itemID	itemID
     InvOrgID	InvOrgID

   • Click the Response Mapping icon, then notice the attributes that the integration maps from target to source.

     

     For example.

     Attribute in Source	Aspect in Target
     Value	Value
     itemCost	itemCost
     CurrencyCode	CurrencyCode
     UOMCode	UnitOfMeasureCode
     ErrorFlag	ErrorFlag
     ItemId	ItemId
     InvOrgId	InventoryOrgId

   • Click the Fault Mapping icon, so notice how the integration maps attributes to handle whatever faults that might occur at run time.

     Aspect	Value
     Mistake	ServiceErrorMessage
     Road To	ServiceErrorMessage

Actuate the Integration

1. On the Integrations page, on the row that contains your integration, click Actions > Edit.

2. On the Map Data Integration page, click Actions > Tracking.

3. On the Business concern Identifiers for Tracking dialog, fix the value, and then click Washed.

   Chief	Tracking Field
   Contains a check marking.	ItemID

4. On the Map Information Integration page, on the condition bar nearly the peak of the page, verify that the status displays 100%.

   The status displays adjacent to the Final Modified attribute.

5. Click Salve, then click Close.

6. On the Integrations page, on the row that contains your integration, click Actions > Actuate.

7. On the Activate Integrations dialog, set values, and so click Activate.

   Option	Value
   Enable Tracing	Contains a cheque marker.
   Include Payload	Contains a check mark.

C. Test the SOAP Service

Test your phone call to the SOAP service.

• Decide the input payloads you lot need.

• Apply SOAP UI to do your test.

• Become the URL for the SOAP web service that you need to do the test from Integration Deject Service. For case.

                  https://ssotest.oracle.com/integration/flowsvc/soap/COSTING_API_PRICING_INTEG/v01/              

• Examine the response payloads.

• Test for more than ane item to brand sure the service returns the correct cost for different types of calculations.

• Include mistake cases during your test to make sure the costing service returns errors correctly through the integration.

Here's an instance input payload yous can utilize to send to the Soap service during the test. Example address to the WSDL.

            https://server.integration.us2.oraclecloud.com/integration/flowsvc/soap/CGB_INTE_ORAC_FUS_PRIC_WITH_ANTH/v01/?wsdl          

Example payload.

            <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/lather/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/types/">    <soapenv:Header>       <wsse:Security soapenv:mustUnderstand="one" xmlns:wsse="http://docs.haven-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open up.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-one.0.xsd">          <wsu:Timestamp wsu:Id="TS-772E6BAE6F9F39812416003717946724">          <wsu:Created>2020-09-17T19:43:14.670Z</wsu:Created>          <wsu:Expires>2020-09-17T19:44:14.670Z</wsu:Expires>          </wsu:Timestamp>          <wsse:UsernameToken wsu:Id="UsernameToken-772E6BAE6F9F39812416003714274653">            <wsse:Username>shailendra.pitre@oracle.com</wsse:Username>             <wsse:Password Type="http://docs.haven-open up.org/wss/2004/01/haven-200401-wss-username-token-contour-ane.0#PasswordText">WedAug05@0@0</wsse:Countersign>             <wsse:Nonce EncodingType="http://docs.haven-open up.org/wss/2004/01/haven-200401-wss-soap-bulletin-security-1.0#Base64Binary">zFzlHdJthMM1ZS5uXnmCcQ==</wsse:Nonce>             <wsu:Created>2020-09-17T19:37:07.465Z</wsu:Created>          </wsse:UsernameToken>       </wsse:Security>    </soapenv:Header>    <soapenv:Body>       <typ:retrieveItemCost>          <typ:CostParams>             <!--Optional:-->             <typ:ItemID>149</typ:ItemID>             <!--Optional:-->             <typ:InvOrgID>204</typ:InvOrgID>             <!--Optional:-->             <typ:UnitOfMeasureCode>Ea</typ:UnitOfMeasureCode>          </typ:CostParams>       </typ:retrieveItemCost>    </soapenv:Torso> </soapenv:Envelope>                      

Here's an example response payload that the SOAP service sends to you. Examine it to make sure ItemCost contains the amount you expect for ItemID and InvOrgID.

            <S:Envelope xmlns:South="http://schemas.xmlsoap.org/soap/envelope/">   <S:Body>     <wss:costServiceResponse xmlns:wss="http://www.boomi.com/connector/wss">       <Value>         <ItemCost>12484.78</ItemCost>         <CurrencyCode>GBP</CurrencyCode>         <UnitOfMeasureCode>Ea</UnitOfMeasureCode>         <ErrorFlag>imitation</ErrorFlag>         <ItemID>100000001582378</ItemID>         <InvOrgID>300000037424187</InvOrgID>       </Value>       <Value>         <ItemCost>11404.41</ItemCost>         <CurrencyCode>GBP</CurrencyCode>         <UnitOfMeasureCode>Ea</UnitOfMeasureCode>         <ErrorFlag>faux</ErrorFlag>         <ItemID>100000001582379</ItemID>         <InvOrgID>300000037424187</InvOrgID>       </Value>     </wss:costServiceResponse>   </Due south:Body> </S:Envelope>          

D. Set the Connector in Oracle Fusion

1. Sign into Oracle Fusion applications.

   In the Navigator, click Setup and Maintenance.

2. In the Setup and Maintenance work surface area, open the job.

   • Offering: Club Management

   • Functional Surface area: Pricing

   • Task: Manage External Service Details for Algorithms

   This case assumes you're setting up the Gild Direction offering. If you utilize a different offer, and then click it instead of Order Management.

3. On the Manage Connector Details folio, create a connectedness to the organization that hosts the spider web service that your pricing algorithm calls. For this example, assume it calls the Oracle Fusion Costing Service.

   Attribute	Value
   Target System	Fusion_HCM You must showtime apply the Setup and Maintenance work expanse to specify this system as a trading customs source system.
   Connector Proper name	QP_FUSION_COSTING_ICS_SRVC You can use any value, but information technology must match the value that the pricing algorithm sends to the executeSOAPService function.
   Connector URL	Enter the URL that locates the server and port that your spider web service uses every bit the end indicate. For example. https://ssotest. oracle.com/integration/flowsvc/soap/COSTING_API_PRICING_INTEG/v01/
   User Proper name	Enter the user name required to admission your web service.
   Password	Enter the password required to access your web service.
   Invocation Mode	Synchronous

   For details, run across the Connect Order Management to Your Fulfillment System topic.

E. Edit the Service Mapping

Add entities to the Sales service mapping. Here's the first ane you lot add.

Make sure you use the exact aspect name and values. If you don't, the mapping will fail.

Try it.

1. Sign into Oracle Fusion Pricing as the pricing administrator.

2. In the Navigator, click Sandboxes.

3. On the Sandboxes, page, open and enter your sandbox, or create a new one.

4. In the Navigator, click Pricing Administration.

5. On the Overview page, click Tasks, then under Pricing Configuration, click . Manage Service Mappings.

6. On the Manage Service Mappings page, click Sales.

7. On the Edit Service Mapping page, on the Entities tab, click Actions > Add Row, then set the values.

   Attribute	Value
   Entity	CostParams_Custom
   Clarification	Store the value for my price parameter extensions.

8. In the Details area, add two attributes. Make certain Allow Null contains a check mark for each attribute.

   Aspect	Value
   InvOrgID_Custom	Long
   ItemID_Custom	Long

9. Add another entity. On the Entities tab, click Actions > Add Row, and so prepare values.

   Attribute	Value
   Entity	Value_Custom
   Description	Store the value of the CostParams input element.

10. In the Details area, add together attributes to the Value_Custom entity. These attributes will incorporate the details that you communicate to and from your external arrangement. Make sure Permit Null contains a cheque mark for each aspect.

    Attribute	Value
    CurrencyCode_Custom	String
    ErrorFlag_Custom	Boolean
    InvOrgID_Custom	Long
    ItemCost_Custom	Decimal
    ItemID_Custom	Long
    UOMCode_Custom	String

11. Add another entity that copies the definition that the spider web service uses. On the Entities tab, click Actions > Add Row, then set up values.

    Aspect	Value
    Entity	Result_Custom
    Description	Store the value of the output element.

12. On the Entities tab, click the row that contains Header in the Entity column.

13. In the Details area, click Actions > Add Row, then set up values.

    Aspect	Value
    Entity	FulfillOrgId_Custom If you use a listing of values in a search dialog to specify the item cost, then you must use a pretransformation to populate the value in the FulfillOrgId aspect.
    Type	Long

14. Click Salvage.

Add the Source to the Service Mapping

1. Click Sources.

2. Add an attribute to the OrderCatalogLine source.

   • On the Sources tab, click the row that contains OrderCatalogLine in the Source column.

   • In the Details area, on the Entity Mappings tab, click the row that contains Header in the Entity cavalcade.

   • In the Details surface area, on the Attribute Mappings tab, click Actions > Add Row, then set the values.

     Attribute	Value
     Attribute	FulfillOrgId_Custom
     View Object Attribute	FulfillOrgId

3. Add together an attribute to the OrderHeader source.

   • On the Sources tab, click the row that contains OrderHeader in the Source column.

   • In the Details surface area, on the Entity Mappings tab, click the row that contains Header in the Entity column.

   • In the Details area, on the Attribute Mappings tab, click Actions > Add Row, then set the values.

     Aspect	Value
     Attribute	FulfillOrgId_Custom
     View Object Attribute	FulfillOrgId

4. Add an attribute to the OrderLine source.

   • On the Sources tab, click the row that contains OrderLine in the Source column.

   • In the Details expanse, on the Entity Mappings tab, click the row that contains Header in the Entity column.

   • In the Details area, on the Attribute Mappings tab, click Deportment > Add Row, then set the values.

     Attribute	Value
     Attribute	FulfillOrgId_Custom
     View Object Aspect	FulfillOrgId

Add the Service to the Service Mapping

Specify the cease point that locates the external service, and specify the entities that you lot will utilize to communicate details with the service.

The screen capture includes.

• The service y'all add together.

• The entities y'all add to the service.

• The Value_Custom entity that doesn't accept a value in the Reference Entity attribute is selected.

• The attributes for the first Value_Custom entity.

Effort it.

1. On the Edit Service Mapping page, click Services.

2. Click View > Columns, then add together a check mark to Alias and Namespace.

3. Click Actions, click Add Row, then gear up values.

   Attribute	Value
   Service	RetrieveItemCost_Custom Yous tin can enter any text. Describe what the service does.
   Allonym	retrieveItemCost
   Implementation Type	Internal
   Namespace	Enter the URL that locates the end indicate on the external organization that will communicate the SOAP payloads with Pricing. For instance. http://xmlns.oracle.com/apps/scm/costing/itemCosts/service/types/ Don't employ http://my_server.com:7012.

4. In the Details area, on the Entities tab, add together the entities. Make sure the Read attribute and the Write aspect for each entity contains a check mark.

   Entity	Alias	Parent
   CostParams_Custom	CostParams	Go out empty.
   Result_Custom	Result	Exit empty.
   Value_Custom	Value	Get out empty.

5. Click Salve.

6. In the Details surface area, on the Entities tab, click View > Columns, then add a bank check mark to Reference Entity.

7. In the Details area, on the Entities tab, add another entity. Make sure the Read attribute and the Write aspect each contain a check mark.

   Entity	Alias	Reference Entity	Parent Entity
   Value_Custom	Value	Value	Result

   The definition of the Oracle Fusion Costing Service includes a three level hierarchy.

                   Root   CostParams and Event     Value              

   To create this hierarchy, you.

   • Add the Value_Custom entity and leave the Parent Entity empty.

   • Add another Value_Custom entity, specify the reference entity as Value, and specify the Parent Entity as Result.

8. In the Entity column, click CostParams_Custom.

9. In the CostParams_Custom Entities expanse, add attributes. Brand sure the Read attribute and the Write attribute for each aspect contains a check mark. Leave other attributes empty.

   Attribute	Allonym
   InvOrgID_Custom	InvOrgID
   ItemID_Custom	ItemID

   The pricing algorithm uses these aliases, and they're case sensitive.

10. In the Details area, on the Entities tab, click the Value_Custom row that doesn't contain a value in the Reference Entity attribute.

11. In the Value_Custom Entities surface area, add together the entities. Brand sure the Read attribute and the Write attribute for each entity contains a cheque mark. Leave other attributes empty.

    Aspect	Allonym
    CurrencyCode_Custom	CurrencyCode
    ErrorFlag_Custom	ErrorFlag
    InvOrgID_Custom	InvOrgID
    ItemCost_Custom	ItemCost
    ItemID_Custom	ItemID
    UOMCode_Custom	UOMCode

12. Click Relieve.

    Information technology isn't necessary to use the Sources tab to create the source because you lot typically use the Sources tab to specify a source when a virtual object populates the web service. Still, in this example, yous utilise a pricing algorithm and call a web service to get the details that the web service needs.

Update the PriceSalesTransaction Service

1. On the Services tab, click Query Past Example, then query for the value.

   Attribute	Value
   Service	PriceSalesTransaction

2. In the Details area, on the Entities tab, click Query By Example, and so query for the value.

   Aspect	Value
   Entity	Header

3. In the Entities area, click Activity > Add Row, prepare values, then click Save and Shut.

   Aspect	Value
   Aspect	FulfillOrgId_Custom
   Read	Contains a bank check marker
   Write	Contains a check marker

F. Troubleshoot

Here are some tips.

• If your pricing algorithm reports a 401 Unauthorized exception while calling the costing service, then utilize a secured service link in the service registration.

• If the price breakdown in Order Management doesn't display your price accuse components, and so yous must add together them. For details, come across the Manage Price Details on Society Lines topic.

• Appraise your algorithm extension to determine whether y'all must modify information technology during an upgrade. For details, see Performing Your Quarterly Update (Doc ID 2337485.i) on My Oracle Support.

Call a Dissimilar Service from the Pricing Algorithm

This topic describes how to call the Costing SOAP service from a pricing algorithm, merely you can telephone call a dissimilar service to meet your specific requirements.

1. Determine whether the schema for your WSDL service must use Integration Cloud Service. Almost Soap services practice crave that you employ Integration Cloud Service.

2. If you don't need Integration Cloud Service, then skip sections B and C.

3. In department D, If you.

   • Don't need Integration Deject Service, prepare the connector so information technology connects straight to the SOAP service.

   • Do need Integration Cloud Service, gear up the connector so it connects directly to Integration Cloud Service.

4. In Stride Due east, set upward the service mappings for each asking schema and response schema of the WSDL.

5. In Step F, set up the algorithm co-ordinate to your deployment requirements.

   • Employ the Pricing Process topic and the Instance of How Pricing Algorithms Cost Items topic to identify the pricing algorithms that y'all must modify.

   • Identify the step in each algorithm where you must call the service.

   • Determine the input values that y'all must employ to then yous tin interface with the service.

   • Determine how you will process the output from the service, including how yous volition apply the algorithm variables to process the output.

sawyeryones1949.blogspot.com

Source: https://docs.oracle.com/en/cloud/saas/supply-chain-management/22a/faupr/get-costs-for-pricing-from-external-systems.html

Share this post