Hi
Define the desired filter conditions using the Administration Console SMOEAC. There, the R/3 System is defined as a site. You can use replication objects, subscriptions and publications to define certain criteria. For a detailed description, see Note 502037.
Note that you may only use the following criteria fields during the generation of a replication object for BDoc type BUS_TRANSACTION_MESSAGE:
BUS_TRANS_MSG_HEADER-OBJECT_ID
BUS_TRANS_MSG_HEADER-PROCESS_TYPE
BUS_TRANS_MSG_HEADER-POSTING_DATE
BUS_TRANS_MSG_ORGMAN-SALES_ORG
BUS_TRANS_MSG_ORGMAN-DIS_CHANNEL
BUS_TRANS_MSG_ORGMAN-DIVISION
To be able to filter the business transaction data, you must delete the existing replication model for business object type BUS_TRANSACTION_MESSAGE and recreate it with filtering allowed.
Perform the following steps:
In your development system:
- 1. Make sure that no new sales documents are created by locking the online user and deregistering all inbound queues of the object type.
- 2. Delete the subscription of publication "All Business Transactions (MESG)" in the Administration Console (transaction code SMOEAC)
- 3. Delete the publication "All Business Transactions (MESG)".
- 4. Delete the replication object "BUS_TRANSACTION_MESSAGE".
- 5. Create a new replication object "BUS_TRANSACTION_MESSAGE" of type "simple intelligent (msg)" and select the relevant criteria fields with the correct operator. (For sales documents, see Note 497434).
- 6. Create a new publication, such as "Sales Documents by Field1 Field2." and assign the relevant criteria fields to it.
- 7. Create a new subscription, such as "Sales Documents by AAA BBB..." for the new publication
- 8. Assign the subscription to the R/3 backend site.
- 9. Unlock the user and re-register the inbound queues.
- 10. Test your changes.
Do not not release the transport request with your changes before you have performed the first two steps below in your test and productive systems.
In your test and productive systems:
- 1. Make sure that no new sales documents are created by locking the online user and deregistering all inbound queues of the object type.
- 2. Delete the subscription for publication "All Business Transactions (MESG)" in the Administration Console.
- 3. Release the transport request with the changes in the development system to transport them to your test and productive systems.
- 4. Generate the runtime data using transaction SMOGPP in your import client (normally client 000)
- 5. Create a new subscription such as "Sales Documents by AAA BBB ..."
- 6. Assign the subscription to the R/3 backend site.
- 7. Unlock the user and re-register the inbound queues.
Note 502037 - Filtering Business Transaction Data in Messaging Flow
Note 497434 - Upload SALESORDER: Filters do not work
Regards,
Vaibhav Shah