IDOC Filtering for DEBMAS

I am currently using change pointers to trigger the DEBMAS IDOC. I need to be able to filter a range of customers that are not required to be sent. These customers have a defined class type, so it would be ideal to prevent these from going through with a <> filter.
I'm looking into the Distribution Model filter, but the options appear limited to Function, Company Code, Credit COntrol Area, Division, Sales Org, Dist Chnl.
Any ideas to exclude this type of customer from the IDOCs being processed would be very much appreciated.
Thank you!
Jaime

Hi,
Using BAPI, you can filterout the customers that not required to process thru ALE.
Filters are conditions that BAPIs have to satisfy so that they can be distributed by ALE outbound processing.
The BAPIs and message types in a model view that are filtered contain a relevant sub-entry.
In the change mode you can define filter groups and values by selecting
Edit -> Display/edit details.
The following types of filtering are possible:
Data Filtering with BAPIs
Prerequisite:
You have defined the filter objects for a specific BAPI and assigned them to the BAPI. For more information see the ALE Programming Guide under Filtering Data.
There are two types of filtering to choose from:
Interface Reduction:
Here optional BAPI parameters and/or BAPI fields are switched off.
You can choose the options:
- Reduce by fields
- Fully reduced
For example, the BAPI RetailMaterial.Clone is called with parameters containing basic data, production data, sales and distribution data, plant data, etc.
If the BAPI is called by a material reference system in a sales and distribution system, only the parameters containing basic data and sales and distribution data have to be transferred.
Content-Dependent Filtering
The rows of the BAPI table parameters which do not satisfy the distribution conditions are filtered out.
Developers can also use field references to define hierarchy relationships between table parameters. Such hierarchies are maintained in the ALE Development menu under BAPI -> Maintain hierarchy for BAPI table parameters.
For furhter details please click on below link:
http://help.sap.com/saphelp_46c/helpdata/en/4f/1c4b6e5733d1118b3f0060b03ca329/frameset.htm
You may try with this info.
Thanks,
Naga

Similar Messages

IDOC filtering for VL02n

Hello all,
I am creating the Delivery03 type IDOC each type a delivery document is changed or created using message control technique. But I want to create the IDOC only for perticular value of the delivery type and shipping point. How can I achive this ? Is there any user exit or badi I can use to implement htis?
Thanks and regards,
Keith

Hi..There is no need of exit for this.
We can Acheive this by maintaining Filter Conditions in BD64.
Steps: in BD64
Double Click on the "Data filter Not Active" under the Message type of Delivery03 in your model View.
Create a Filter Group
Maintain these Conditions
Note: If there are no filter objects available for Delivery type or Shipping point we can maintain them in BD95. And then they will Appear in BD64.
let me know if there are any issues.
Reward if Helpful

IDOC filtering for VLO2N PGI interface

Hello everyone,
we have an outbound interface online. An idoc is generated on PGI in VL02N (Interface ART_DVT).
We have another outbound interface which generates an IDOC for deliveries (Interface ART_OUT).
Both these interfaces update a table in a third party system.
As per my current requirement, the PGI interface should be triggered only for deliveries for which ART_OUT has been triggered.
The ART_DVT interface is being triggered via message control NACE.
Message Type : DELINF
Basic Type : DELVRY05
Whenever ART_OUT is triggered, a z-table gets updated in SAP with the necessary details.
I think I can check here before triggering the ART_DVT interface if i could use an user-exit in VL02N.
Any help is appreciated.
Thanks in advance.
Regards,
Xineohpi

Can someone atleast tell me if there is an user-exit or badi using which i can restrict the PGI idoc generation based on some check or if the message control execution part can be restricted..
in dire need of help......
Regards,
Xineohpi

Out bound idoc for debmas

Can any one send me sample program for
DEBMAS Idoc outbound proces with change pointers

Hi,
Check this link for details :
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
check these steps :
1.Go to the Data Element of the field and check whether change doucment option is checked or not .
2.change the value of the field and check the entries in CDHDR and CDPOS.here u can check the change document object and table .
3.check BDCP table also incase of ALE.The program RBDMIDOC generates IDOc when there is an entry in BDCP.
if not check the following config
1.BD61- change pointers activated -generally
2.BD50 -Activate change pointers for ur message type
3.BD52 - add the triggering fields and corresponding tables and change document object.
Please check the entries in BDCP table ,if u find the entries execute the program RBDMIDOC
Regards
Appana
*Reward Points for useful answers

Working on IDOC OUTBOUND FOR Vendor Master and Customer Master

Hi Group,
I need to create IDOC's for Vendor master and customer master using ALE. Whenever they create vendor/customer or changes to vendor/customer should create IDOC's.
Can anyone please help me out how to proceed? I know that we can use CREMAS/DEBMAS and CREMAS04/CREMAS...But I would like to know how to use those.
Thank-You,
Venky

Hi Sai,
Welcome to group.
Related to CREMAS/DEBMAS, for your situation, you can use the change pointers. With this, when ever there is an change/create, it will create an entry in CDHDR & CDPOS and based on that it will create the IDOCs for these.
Activate the change pointers for these message types and run the application RBDMIDOC periodically (whenever you want). This application will create the IDOCs based on your entries.
To activate the change pointers, the TCODEs are
BD50 Checking change pointer is activated for Message Type
BD52 Checking which fields are configured change pointer to create. (please make sure, an entry will exist in BDCP table)
I hope you know the remaining configuration related to partner profile entries (WE20) i.e. to which system you want to send the idocs and Inbound or Outbound etc.
Let me know if you need further info.
shylesh

Idoc Type for Vehicle Master

Hi Friends,
Can any body tell me the Idoc type for
1. Vehicle Master 2. Transport unit and their respective transaction code to send data.
Points would be awarded for useful answers.
With Regards
Vasu

Hi,
Please maintain distribution model (BD64) and partner profile (WE20), RFC connection (SM59) for message type DEBMAS (customer), DEBMAS (vendor) and MATMAS (material master).
Once the above configuration done, then you can use the following transactions to send the IDocs.
1. BD12 - Send Customer IDocs (Sender -> Receiver) or
     BD13 - Get Customer IDocs (Receiver -> Sender)
2. BD14 - Send Vendor IDocs (Sender -> Receiver) or
     BD15 - Get Vendor IDocs (Receiver -> Sender)
3. BD10 - Send Material IDocs (Sender -> Receiver) or
     BD11 - Get Material IDocs (Receiver -> Sender)
Regards,
Ferry Lianto

Why customer master idoc named like DEBMAS?

hi,
i am just curious know why customer master idoc named like DEBMAS?
vendor master data idoc as cremas?
any German abbreviation or English abbreviation behind this will be appreciated.
thanks & regards
Raja
Message was edited by:
Raja

To my knowledge I do not think that the naming has anything to do with the German translations since in German:
Customer = Kunde and
Vendor = Verkäufer....
However the naming has some connection with the Business Case behind customers and vendors. In SAP, a customer is a business partner whose account you debit for money, hence the name DEBMAS and a vendor is a business partner whose account you credit money, hence the name CREMAS.
PS: Reward points and close the question if you find this helpful.
Regards.

IDOC Filtering

Hi ,
I have a Requirement on the Field Level IDOC Filterring.
The Query Goes as Follows, this is and( OUTBOUND FLOW):
In the MATMAS IDOC, with Segment : E1MARCM, Filed PERKZ ='5', then this idoc should not trigger.
Please let me know is ther any Filtering where the PERKZ = 5 then the IDOC should not Trigger.
Note : I dont want to write any user exits or Program for this.
Thanks in Advance.
Regards,
Praveen Kalwa

Hi ,
I have a Requirement on the Field Level IDOC Filterring.
The Query Goes as Follows, this is and( OUTBOUND FLOW):
In the MATMAS IDOC, with Segment : E1MARCM, Filed PERKZ ='5', then this idoc should not trigger.
Please let me know is ther any Filtering where the PERKZ = 5 then the IDOC should not Trigger.
Note : I dont want to write any user exits or Program for this.
Thanks in Advance.
Regards,
Praveen Kalwa

BADI for DEBMAS

Hi experts,
Scenario is from SAP to PI and then 3rd party system :IDoc to JDBC.
Now for triggering IDocs for DEBMAS , standard configuration settings of ALE is maintained in ECC. Through BD21 IDoc is getting triggered. Also there is standard BADI has been used to trigger IDoc.
Can you provide me BADI name that has been used for DEBMAS. Also in PI messages failed due to missing E1KNB1M segment .
This is because in PI, Receiver determination : condition is there : The E1KNB1M is a mandatory field in PI . The IDOC which failed doesnu2019t have this mandatory field.(BUKRS) Company Code . Although in BD52, in message type , BUKRS field is present.
Kindly let me know how to resolve this issue . Its related with configuration settings and BADI. But i dnt know BADI name . where we can customized code . In this interface everything is standard .
Thanks in advance.
Best regards,
Asha

Hi,
just goto tx SMOD and look for enhancement components V*.
There is also one enhancement for debitors.
Cheers,
André

What is Ale, Edi,IDoc tech for sap

Hi all,
What is Ale, Edi,IDoc tech for sap?
Thanks.

hi deniz,
<b>ALE</b>
ALE
Triggering OB via Change Pointers:
      When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
Outbound Process:
When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
     To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
Asynchronous Communication:
The data that is IDocs and the function module are stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
Inbound Process:
The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
     Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
In the table TBD51 there will be entries to find which option is used.
Transactions:
SALE - IMG ALE Configuration root
     WE20 - Manually maintain partner profiles
     BD64 - Maintain customer distribution model
     BD71 - Distribute customer distribution model
     SM59 - Create RFC Destinations
     BDM5 - Consistency check (Transaction scenarios)
     BD82 Generate Partner Profiles
     BD61 Activate Change Pointers - Globally
     BD50 Activate Change Pointer for Msg Type
     BD52 Activate change pointer per change.doc object
     BD59 Allocation object type -> IDOC type
     BD56 Maintain IDOC Segment Filters
     BD53 Reduction of Message Types
     BD21 Select Change Pointer
     BD87 Status Monitor for ALE Messages
     SALE Display ALE Customizing     WEDI - ALE IDoc Administration
     WE60 - IDoc documentation
     SARA - IDoc archiving (Object type IDOC)
     WE47 - IDoc status maintenance
     WE07 - IDoc statistics
BALE - ALE Distribution Administration
     WE05 - IDoc overview
     BD87 - Inbound IDoc reprocessing
     BD88 - Outbound IDoc reprocessing
     BDM2 - IDoc Trace
     BDM7 - IDoc Audit Analysis
     BD21 - Create IDocs from change pointers
     SM58 - Schedule RFC Failures
<b>EDI</b>
EDI(Electronic Data Interchange )
RFC DESTINATION:
                       A logical name used to identify the remote system on which a function needs to be executed.
Partner Profile:
      It defines the characteristics of data being exchanged with the business partner.
Partner Function:
     Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
Partner type:
          The type of your business partner .
     EDI         KU/LI
     ALE     -- LS.
Archiving:
     -Need to archive the important transmitted document
-Created in SARA
     -Assigned in WE20.
PartnerProfile Tips:
     RSECHK07- Consistency check for Partner Profile.
     If you want to modify partner profile; copy it and then modify. If you cant modify it , u have to delete it.
     To move partner profile to production system choose Partner -> Transport
Port defintion:
     It defines the medium through which data is exchanged between systems.
     tRFC    -   Used by ALE
     FILe     -   Used by EDI
     R/2 system system port For R/2 system
     Internet port           - to connect with internet applications
     It also depends on the receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
Startrfc                                         -   Program to execute RFC enabled Fun.mod. in SAP
EDI_DATA_INCOMING             -   To send data as inbound
EDI_STATUS_INCOMING         -   To send status to SAP
RSPARAM               -   To know the gateway service of the SAP system.
Message Control:
     Output controller
     A service program for determining the output type
     To generate and manage various outputs from an application and control their medium and timing of exchange.
     To retransmit the document without duplicating it
Procedure:
     A procedure defines a set of possible outputs for an application
     There may be more than one procedure but only one can be active
     Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
Output type:
Defines the characteristics and attributes of the output.
Access Sequence :
Defines a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
Sapfans Q & A
SREL_GET_NEXT_RELATIONS   -
Function Module that will provide me the number of the document that was created by an IDoc
RLSUB020
Program which uses the above function module.
Upgradation problem
When the old version program is upgraded in to newer version(4.0b  4.6c) the SE38 editor wont allow u get thru the programs normally to get rid of this.
Solution:
EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
this fixes the links
ALE( Application Link Enabling )
Disk Mirroring:
Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disks contents.
Replicas:
Maintaining redundant data across multiple systems.
ALE:
It provides distributed environment to integrate non-SAP systems
Provides guaranteed delivery of data regardless of network problem to application.
Logical system :
     The systems involved in distributed environment are assigned a logical name which uniquely identifies a system in a distributed environment.
Data Mapping:
     Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
Message Types:
     Represents a business function
     Technical structure is the IDoc type
     Or can say an instance of IDoc.
<b>IDoc :</b>
     They are containers used to exchange data between any two process.
     It represents an IDoc type and IDoc data
     IDoc type is structure and IDoc data is an instance of it.
<b>Pls reward if helpful.</b>

How to find the number of idocs generated for a customer on the basis of his purchase order in a day ?

How to find the number of idocs generated for a customer on the basis of his purchase order in a day ?

Dear Friends,
I am absolutely agree with your answer .
But my question is,
Lets say.....
One customer sending X number of purchase orders in a day , so how many IDocs generated on that specific day for that specific customer .
So, Question is , How can we find the no of sales orders(IDocs) generated for the customers on the specific day ?
Hope you all understood my requirement .
Thanks & Regards,
Aditya

BCExeption: The IDOC metadata for null is not available in SID

<h3>Hello Guys,</h3>
we need some information about the error message:
com.wm.pkg.sap.BCExeption: The IDOC metadata for null is not available in <SID>
We use a Business Connector 4.8 and the backend is an ECC 6.0, we have an inbound xml scenario with FTP.
We pick up the ORDRSP from the vendors ftp-server and we would like to drop it to our backend system.
We can read the xml file into a string, but not send to the backend system, we use following steps:
- bytesToString
- stringToDocument
- documentToRecord
- recordToIDOC
- lockSession
- createTID
so far works perfekt
- sendIDoc
- releaseSession
On the step "sendIDoc" we see the described error message, but what is the message from the message?
Any Ideas?
Thank you and regards,
Michael

Hello Michal,
thank you for your quick answer!
In my opinion, i don't need any input for this service, because we pick up all data from the vendors ftp - server in a definied time interval.
All needed fields are available in the xml file. In the result tab is the IDocList filled correct, but no sending to the backend system because the error is displayed.
Is it a problem with my concept?
Regards,
Michael

Standard IDOCS, Programs for posting FI & bank related data.

Hi,
(1)Are there any idocs available for posting FI documents, Vendor master?
(2)Are there any outbound idocs, programs for sending data to banks. EG:positive pay etc?
Kindly reply to these questions. Correct answer will be awarded points.
Regards,
Akshaya.

Hi,
There is message type BANK_CREATE for posting the FI related Bank details. Using the change pointers you can trigger the idocs for posting the bank related data.
Regards,
Uday

Single idoc generation for multiple sales orders

Hi,
Pls let me know how do we generate single idoc for multiple sales orders.
Its not collecting idoc. As we know we can generate an idoc for one sales order correspondingly
my requirement is to generate single idoc number for multiple sales orders.
Do we need to write a program.

Amar,
To understand take HRMD_A04 as example. Root segment has Maximum 9999999999 defined.
Segm.type E1PLOGI
Minimum number 1
Maximum number 9999999999
Parent segment
Hier.level 2
This means that this IDOC types has capability to hold multiple HR Master data objects. PFAL program creates this IDOC and it has facility to mention the Objects per process, check selection screen.
I checked for INVOICE01/02 its not possible there. Hope this clarifies.

RSAR2318 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Error RSAR238 : IDoc type for source system T90CLNT090 is not available
I have already checked trx & dtps, but could not find resolution.
Kindly help me with this error.
Thanks and regards,
MS

M Sharma wrote:
But how exactly can I create when T90CLNT is not active? Help please.
Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

IDOC Filtering for DEBMAS

Similar Messages

Maybe you are looking for