Find Production Order by Work Centre - response time too long

[Former Member]

Scenario: external MES -> PI -> ECC-Backend

External MES calls Enterprise Service "Find Production Order by Work Centre" (ECC_PRODUCTIONORDERSWQR)

http://es-workplace.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?packageid=DE0426DD9B0249F1...

The MES selects for one Plant, one Workcentre, Status="FREI" and Status<>"LÖVM"

First call runs into timeout after 60s.

Response time of second and further calls is between 20 and 30s. There are about 10 production order id in the Response.

Some time later service call runs into timeout again.

PI is 7.11

ECC is 6.0 EHP13

I need Response time lower than 3s.

Has anybody an idea?

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
   <soapenv:Header/>
   <soapenv:Body>
      <glob:ProductionOrderSimpleByWorkCentreQuery_sync>
         <ProductionOrderSimpleSelectionByWorkCentre>
            <ERPProductionOrderRequiredIndicator>true</ERPProductionOrderRequiredIndicator>
            <ERPProcessOrderRequiredIndicator>false</ERPProcessOrderRequiredIndicator>
            <SelectionByWorkCentreID>
               <InclusionExclusionCode>i</InclusionExclusionCode>
               <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode>
               <LowerBoundaryWorkCentreID>80050020</LowerBoundaryWorkCentreID>
            </SelectionByWorkCentreID>
            <SelectionByPlantID>
               <InclusionExclusionCode>i</InclusionExclusionCode>
               <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode>
               <LowerBoundaryPlantID>662L</LowerBoundaryPlantID>
            </SelectionByPlantID>
            <SelectionBySystemStatusName>
               <InclusionExclusionCode>i</InclusionExclusionCode>
               <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode>
               <LowerBoundarySystemStatusName languageCode="DE">FREI</LowerBoundarySystemStatusName>
            </SelectionBySystemStatusName>
            <SelectionBySystemStatusName>
               <InclusionExclusionCode>e</InclusionExclusionCode>
               <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode>
               <LowerBoundarySystemStatusName languageCode="DE">LÖVM</LowerBoundarySystemStatusName>
            </SelectionBySystemStatusName>
         </ProductionOrderSimpleSelectionByWorkCentre>
      </glob:ProductionOrderSimpleByWorkCentreQuery_sync>
   </soapenv:Body>
</soapenv:Envelope>

[Former Member]

There is a wrong link to es-workplace in my posting:

This link should point to

Find Production Order by Work Centre

And the correct "Related Web Service Definition" is ECC_PRODUCTIONORDERSWQR

[arunneerolil]

Test the service "Find Production Order by Work Centre" (ECC_PRODUCTIONORDERSWQR)

from SPROXY and find out how long does it takes to respond.

If it takes too long, then you will have to work with Basis guys to fix it. May be you can route the traffic to an instance of low load.

regards, Arun

[Former Member]

I called the service with soapui directly at the service endpoint of ECC system and got the same long response time as over PI.

At PI-Monitoring it looks like as well, that the long response time is caused by ECC system.

I never worked with SPROXY. I have permission to start it. But when I go to "Enterprise Services Browser" -> ProductionOrderSimpleByWorkCentreQueryResponse_In

then I get "You don't have permission ...

At the ECC system, I'm using, there is no load.

Other SAP enterprise services respond within 1s.

There is an individual coded ABAP Proxy at the same ECC system, which finds same information within 1s. Our SAP Team want's to reduce the amount of individual code. That's why I'm trying to get the production orders with SAP enterprise Service.

Our SAP Basis gyus don't know SAP enterprise Services.

[Former Member]

If I don't use StatusName-filtering in the servie request, then the ECC system delivers about 1.500 production order id within 1s.

But the MES has to read the production order Details in next step. That's why it can't deal with 1500 production order id.

[RaghuVamseedhar]

Roland,

Can you please let us know how long ABAP program takes to give response (test in SAP ECC). Then test interface from SAP PI to SAP ECC and end to end, note how long it takes. If ABAP program takes more time, request ABAP team to fine tune it. If it takes more time from PI to ECC or MES to PI, request network team for more information/resolution.

[Former Member]

How can I find out, which ABAP program SAP calls for its Enterprise Services?