Defect Tracking API data posted from CPI to S4 shown in Table QMFE but not in TCode QF21

[AHMED786]

Hi Experts,

There is one requirement to post the data using the defect tracking API which is successful from CPI to S4 with below details

/sap/opu/odata4/sap/api_defect/srvd_a2x/sap/defect/0001/Defect

<Defect>

<Defect_Type>

<DefectInternalID>00000000004</DefectInternalID>

<DefectText>test1</DefectText>

<DefectCodeCatalog>9</DefectCodeCatalog>

<DefectCode>1</DefectCode>

<DefectCodeGroup>QM-E</DefectCodeGroup>

<ManufacturingOrder>000012</ManufacturingOrder>

<InspectionLot>40000000008</InspectionLot>

<DefectCategory>01</DefectCategory>

</Defect_Type>

</Defect>

Even tried with all the 50+ fields of the API populated with the functional data provided but still the same issue.

The post is successful and we can see the data triggered from CPI in S4 in the actual table QMFE and even the GET API call also shows the values posted but its not reflecting in the actual TCODE QF21

If the functional owner is entering any data manually its also available in both backend table QMFE and TCODE QF21 but its not available in GET API call.

Does anyone know any case like this where the API is not working as expected.

Thanks,

Ahmed

[HakanHaslaman]

Looks not working as expected. Possible reasons could be:

1. Data Synchronization: Delay or problem with data sync between QMFE and TCODE QF21 due to a system glitch or software bug.

2. API Configuration: Incorrect API settings or parameters not reflecting changes in TCODE QF21.

3. Data Mapping: Issues with data mapping between the API and TCODE QF21 due to incorrect or missing rules.

4. Authorization: API unable to update TCODE QF21 due to insufficient permissions or access rights.

5. Software Bug: A coding error or design flaw causing the issue.

The best will be to open a support ticket.

[HakanHaslaman]

Looks not working as expected. Possible reasons could be:

1. Data Synchronization: Delay or problem with data sync between QMFE and TCODE QF21 due to a system glitch or software bug.
2. API Configuration: Incorrect API settings or parameters not reflecting changes in TCODE QF21.
3. Data Mapping: Issues with data mapping between the API and TCODE QF21 due to incorrect or missing rules.
4. Authorization: API unable to update TCODE QF21 due to insufficient permissions or access rights.
5. Software Bug: A coding error or design flaw causing the issue.

The best will be to open a support ticket.