cancel
Showing results for 
Search instead for 
Did you mean: 

Filter on message types

Former Member
0 Kudos

Hello Guys,

I have to filter 'WERKS' (Plant) on message types - /SAPSLL/BOMMAT_SLL, /SAPSLL/PRCMAT_SLL and /SAPSLL/PSDMAT_SLL. In BD61 , the change pointers are activated. In BD50 the following message types are enabled.

1. I have an entry for WERKS in BD95.

2. In BD53, I created reduced message type '/SAPSLL/BOMMAT_SLL' with message type reference 'LOIBOM' (Bill of material) and selected segment type 'E1MASTL'.

3. In BD59, I created a new entry for /SAPSLL/BOMMAT_SLL. The new entry is ALE OBject type - WERKS', Segment type - 'E1MASTL', Field - 'WERKS' and saved the entry.

My questions:

1. Are the above configuration steps correct?

2. What message type reference values do I give when creating 'Reduced message types 'SAPSLL/PRCMAT_SLL and /SAPSLL/PSDMAT_SLL'?

Please help.

Thanks...

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member215181
Active Contributor
0 Kudos

Hi Sachin,

Reduced Message Types are useful if you want to reduce the amount of data in the iDocs that are created for Master Data distribution. But data transfer to GTS does not use iDocs.

Instead, you should use Transaction BD52 to configure the "trigger fields" for creating Change Pointers, to include only those that are useful to consider for transfer to GTS . The data set actually transferred is entirely dependent on the Function Module that you assign to each Message Type in Transaction BD60.

As for filtering, you have two options:

1. Code the Use-Exit that is called by the Function Module (e.g. EXIT_SAPLSLL_LEG_PRR3_002 for Message Type /SAPSLL/PRCMAT).

2. Code the BAdI BDCP_BEFORE_WRITE - see the IMG Activity "Reduce Change Pointers for Message Type".

Option 1 avoids transferring data for Change Pointers that have been written for data that does not meet your criteria.

Option 2 prevents Change Pointers from being written when your criteria are not met.

I hope that helps.

Best regards,

Dave