bulking packaging

[ottfro1]

Issue description

bulking packaging is an important feature in SAP PO

nothing is mentioned in the docs for SAP CI

If missing feature it should be mentioned.

If existing - how to configure?

Feedback Type (Optional)

None

Page Title on SAP Help Portal (prefilled)

Configure the IDoc Receiver Adapter

Page URL on SAP Help Portal (prefilled)

https://help.sap.com/docs/cloud-integration/sap-cloud-integration/configure-idoc-receiver-adapter

[SrutiSagaram]

Hi @ottfro1

Thank you for your feedback. We are looking into it, and will get back to you.

[pe-gu]

Thanks for your question! We will discuss the request and get back to you as soon as we have more specific information. I will keep open this issue until this.

[pe-gu]

Hello @ottfro1, in the meantime, we have updated the documentation of IDoc sender adapter and IDoc receiver adapter. Additionally, we provided an integration flow design guideline for handling bulk messages:
Handle IDoc Bulk Messages
I will therefore close this issue.
Many thanks for your contribution!

[pe-gu]

Thanks for your contribution!

[ottfro1]

Dear Peter In PI on the idoc receiver adapter you specify Packaging required X Package Size : N Package Wait Time milliseconds : N Package Memory bytes : Queue processing : Where are the parameters configured in SAP CI? See screenshot ***@***.*** Från: Peter Gutsche ***@***.***> Skickat: den 10 april 2024 08:53 Till: SAP-docs/btp-integration-suite ***@***.***> Kopia: Frost, Otto ***@***.***>; Mention ***@***.***> Ämne: Re: [SAP-docs/btp-integration-suite] bulking packaging (Issue #43) Du får inte e-post ofta från ***@***.******@***.***>. Se varför det här är viktigt.<https://aka.ms/LearnAboutSenderIdentification> Hello @ottfro1<https://github.com/ottfro1>, in the meantime, we have updated the documentation of IDoc sender adapter and IDoc receiver adapter. Additionally, we provided an integration flow design guideline for handling bulk messages: Handle IDoc Bulk Messages<https://help.sap.com/docs/integration-suite/sap-integration-suite/handle-idoc-bulk-messages> I will therefore close this issue. Many thanks for your contribution! - Reply to this email directly, view it on GitHub<#43 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASYVSHZPH572L2YX2MGXFVTY4TOTVAVCNFSM6AAAAABCZ2UKKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBWGY2TINZUGI>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[pe-gu]

Hello @ottfro1https://github.com/ottfro1,
let me notice that the features supported by the IDoc adapter in SAP Integration Suite/Cloud Integration do not 1:1 match to those of the PI/PO (on premise Process Integration) IDoc adapter.
Regarding your question, the IDoc receiver adapter (SAP Integration Suite/Cloud Integration: Configure the IDoc Receiver Adapter | SAP Help Portal) doesn’t support packaging in the way that the adapter waits for messages until either the maximum package size is reached or until the time to send all collected packages as bulk is exceeded.
If you like to implement a similar behaviour, you need the Aggregator step (Define Aggregator | SAP Help Portal) as stated in the documentation.
The following parameters of the Aggregator step support the configuration of completion criteria:
• Completion Timeout (the maximum time between two messages before aggregation is being stopped)
• The Aggregator also doesn’t support a maximum message size. But with the parameter Last Message Condition (XPath), you can define the last message of a composite.
Does this help to answer your question?
Best regards,
Peter

[ottfro1]

Hi Peter, This is very bad information. We need full performance and easy implementation like we have with the bulking/packaging features in the SAP PO idoc adapter. You just check the bulking/packaging check box and it just works. bulking/packaging give about 5 times better performance compared to sending individual messages - if your abap stack has 10 app servers today with sap po - with sap ci you may need 50 servers due to the inefficient idoc processing. The links you refer to for sap CI is very difficult to implement and requires massive and difficult redesign. Migrating to CI fells like going backwards and downgrading. Från: Peter Gutsche ***@***.***> Skickat: den 10 april 2024 16:55 Till: SAP-docs/btp-integration-suite ***@***.***> Kopia: Frost, Otto ***@***.***>; Mention ***@***.***> Ämne: Re: [SAP-docs/btp-integration-suite] bulking packaging (Issue #43) Hello @ottfro1<https://github.com/ottfro1>https://github.com/ottfro1, let me notice that the features supported by the IDoc adapter in SAP Integration Suite/Cloud Integration do not 1:1 match to those of the PI/PO (on premise Process Integration) IDoc adapter. Regarding your question, the IDoc receiver adapter (SAP Integration Suite/Cloud Integration: Configure the IDoc Receiver Adapter | SAP Help Portal<https://help.sap.com/docs/integration-suite/sap-integration-suite/configure-idoc-receiver-adapter>) doesn't support packaging in the way that the adapter waits for messages until either the maximum package size is reached or until the time to send all collected packages as bulk is exceeded. If you like to implement a similar behaviour, you need the Aggregator step (Define Aggregator | SAP Help Portal<https://help.sap.com/docs/integration-suite/sap-integration-suite/define-aggregator>) as stated in the documentation. The following parameters of the Aggregator step support the configuration of completion criteria: * Completion Timeout (the maximum time between two messages before aggregation is being stopped) * The Aggregator also doesn't support a maximum message size. But with the parameter Last Message Condition (XPath), you can define the last message of a composite. Furthermore, Does this help to answer your question? Best regards, Peter - Reply to this email directly, view it on GitHub<#43 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASYVSH553DHUPTDJDB2BZELY4VHCRAVCNFSM6AAAAABCZ2UKKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBXG43TONJXGQ>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[pe-gu]

Hello @ottfro1,
This repository is only used to review feedback on documentation.
Based on your initial feedback, we enhanced the documentation and designed an integration flow design guideline with an example integration flow.
Your remaining questions are related to product enhancements which we can’t address through this channel.
To enter a feature requirement, you can go to the Influence Portal – but please check if a similar request exists and, if yes, vote for it.
See also our Dos and Don'ts.
Thank you.
Best regards,
Peter

[pe-gu]

Thank you for your contribution!