eSOA MaterialCRMChangeRequest_In FEH new requirements
[Asynchronous] [Discard] [FEH] [MaterialCRMChangeRequest] [new in town] [new kid in town] [requirements] [requirements to] [Retry] [Service] [SOA]
- eSOA MaterialCRMBulkCreateRequest_In FEH new requirementsSymptom SOA – FEH MaterialCRMBulkCreateRequest Asynchronous service. “Retry” and “Discard” need to be enhanced. Message header and Log handling need to be enhanced. Other terms SOA, FEH, MaterialCRMBulkCreateRequest Asynchronous Service, Retry, Discard,...
- eSOA ServiceProductCRMBulkCreateRequest_In FEH new reqSymptom SOA – FEH ServiceProductCRMBulkCreateRequest Asynchronous service. “Retry” and “Discard” need to be enhanced. Message header and Log handling need to be enhanced. Other terms SOA, FEH, ServiceProductCRMBulkCreateRequest Asynchronous Service, Retry, Discard,...
- eSOA ServiceProductCRMChangeRequest_In FEH new reqSymptom SOA – FEH ServiceProductCRMChangeRequest Asynchronous service. “Retry” and “Discard” need to be enhanced. Other terms SOA, FEH, ServiceProductCRMChangeRequest Asynchronous Service, Retry, Discard. Reason and Prerequisites SOA – FEH ServiceProductCRMChangeRequest Asynchronous Service,...
- eSOA ServiceProductCRMCreateRequest_In FEH new reqSymptom SOA – FEH ServiceProductCRMCreateRequest Asynchronous service. “Retry” and “Discard” need to be enhanced. Other terms SOA, FEH, ServiceProductCRMCreateRequest Asynchronous Service, Retry, Discard Reason and Prerequisites SOA – FEH ServiceProductCRMCreateRequest Asynchronous Service,...
Symptom
SOA – FEH MaterialCRMChangeRequest Asynchronous service. “Retry” and “Discard” need to be enhanced.
Other terms
SOA, FEH, MaterialCRMChangeRequest Asynchronous Service, Retry, Discard
Reason and Prerequisites
SOA – FEH MaterialCRMChangeRequest Asynchronous Service, “Retry” and “Discard” are not working properly
Solution
1.Regenerate asynchronous service MaterialCRMChangeRequest_In in PO5
2.Confirming a message in forward error handling (enhance IF_ECH_ACTION~FINISH)
3.Discarding a message in forward error handling (IF_ECH_ACTION~FAIL)
4.Repeating a message in forward error handling (extend internal_inbound structure by message header ID and UUID)
5.Forward error handling with post-mapping data (extend internal_outbound structure by message header ID and UUID)
6.Several retries for same message in forward error handling (verify if
buffer is clear at the end of CALL_BUSINESS_LOGIC)
————————————————————————
|Manual Pre-Implement. |
————————————————————————
|VALID FOR |
|Software Component BBPCRM BBP / CRM |
| Release 700 Until SAPKU70003 |
————————————————————————
Caution: You have to perform this manual pre-implementation step manually and separately in each systembeforeyou import the Note to implement.
1. Regenerate the aynchronous service MaterialCRMChangeRequest_In and MaterialCRMConfirmation_Out in
PO5.
2. Modify structures PRD_MATL_CREATE_INB and PRD_MATL_DETAIL_OUT by extending them with a component MESSAGE_HEADER of type CRMST_MESSAGE_HEADER if not yet been done.