IDOC reduction for MSG type MATMAS

HI all,
i have a requirement where clients need only some standard segments and some particulars staructure.We are using MATMAS as a message type and MATMAS05 as a basic type.Basically it leads us for IDOC reduction. Can someone pls help me out for getting this requirement.
Rgds,
Raghav
Edited by: raghav on Jun 9, 2009 12:28 PM

Hi,
Launch the BD53 transaction (IDoc Reduction Maintenance: Initial Screen). In the Reduced message type field, type the value ZVISTAPM_REDUCED, then press the Create button. In the popup window which appears, type in the Message type reference field the value MATMAS.
Validate.
In the next popup window, type a short description for the new reduced message type.
Validate.
In the following window, select the segments and the fields needed for the new reduced message type.
Save.
KR Jaideep,

Similar Messages

1 request Idocs created for message type MATMAS

Hi Experts
I have done necessary config.
I have attempted BD10 and BD11.
I have got message that "1 request Idocs created for message type MATMAS"
But iam unable to find the material in target system.
Please suggest what need to be done.
regards
ramSiva

Marias,
And in PI, after having changed the password (why not), have you unlock this user account ? in SU01 of PI, you have a lock button.
if you did it, and changed also the password, as explained, you have perhaps another (or several) program like a RFC destination which uses another password, and so after some exchanges... with a bad/old password, you have your message "too many...", and then the user is again locked...
If you change the password in PI, you should change it in all application which uses this user. I hope you have not the same user from ECC to PI, than from a third-party to PI...
that's why: the use of such technical users have to be referenced in a doc. By this way, if password has to modifiy, we know where we have to update it (mainly in different RFC destination).
Mickael
Edited by: Mickael Huchet on Dec 5, 2011 5:33 PM

0 idocs generated for msg type cosmas

Hi everyone..
please help out with this idoc issue
I'm trying to send data with msg type COSMAS from 800 to 810 using BD16 as follows:
it just says 0 idocs generated.
I have again gone back and checked my customizations but can't figure it out.
the steps i have done are:
create and assign logical systems
open rfc connections from both c800 and c810
create model view and assign msg type in bd64 in c800.
create partner profiles in both c800 and c810.
open port from c800 .. .DO i have to open a port from c810 as well??
Some doubts I have :
do i have to do :
"Generate the partner profiles by selecting the navigation path from the main menu, Environment --> Generate Partner profiles"
from BD64 after i create the model view and add msg type COSMAS.
regards,
allwyn

HI
no, i have not done anything relating to bd64 in c810 ..that wasn't mentioned in the notes I am following .. Do I have to repeat the same steps like I did in c800?

Problem LSMW + IDOC method for message type : MATMAS

hi friends,
I am using LSMW + IDOC method Message : MATMAS , idoc type : MATMAS03 .Setting every thing are fine. Finally Material is not created with error "message have been issued number : <idoc number>".
data : material, industry type, material type, description, Basic unit of mesure.
Please help me.
Balaji.T.

Hi,
I have nothing found regarding your issue. But maybe a look at SAP note 638058 will give you a hint.
Regards,
Klaus

Error MSG : Create a partner profile for message type 'MATMAS'

Getting Error MSG : Create a partner profile for message type 'MATMAS'
While running LSMW Idoc generation process

See the below link and it has all screen shots how to configure ALE like partner profile,logical systems,RFC
http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html

How to send IDOC with extended message type MATMAS

Hi Experts,
I am looking for a solution to send open PR & open PO related data for diffrent materials through as IDCO in XML file.
Scenario is i have to show a report in a 3rd party system for open PR & open PR that too will come after selection some materials. That means select a materials & it will show all the open PO & related data in a report.
The rough idea for the solution i got is I can save the data in XML file in the system. For this i have to send IDOC. but the problem is there is no message type for PR. IF i am not wrong i can extend the MATMAS05 for a segment that will have PR related info.
Now what to do with that how to send the IDOC do i need to create another report to send IDOC or i can send the extended one through BD10. I tried it but it shows error message "0 communication idoc sent" so I dont no y such error is coming i think i am not filling the extended idoc. But again my QUestion is how to do that.
Can i use BAPI also for such work, if then how it can be helpful.
If anyone have any other solution Please help me out of this.
Regards,
Nik

Hi Mahesh,
Thanks for your reply.
My requirement is bit different. i have to send Open PR data for diffrent materials. In a 3rd party application user will search for few materials which will generate a report that will show the PR related data for those material.
That means for few selected materials there will be few PR's which may be open, i have to show those in my report.
Eg: material A, B. are in PR 00001 & material B, C in PR 00002.
After selecting materials A to C report will show
Material                 PR No                   Item No                Quantity
A                           00001                    10                             1
B                           00001                     20                            3
B                           00002                     10                            3
C                           00002                      10                           1
Same thing i have to do for open PO & open Sales order also.
Can u please help me to provide the solution how can i proceed for it. U have given the Message type & a bapi how it will help in my issue?
I got a suggesion from someone that extend message type matmas for PR, PO, SD related data & send the idoc. but i am confused how to pass that much data ina single IDOC.
Regards,
Nik

IDOC reduction for ORDERS05

Hi,
Is it possible to reduce the idoc for ORDERS05? I used BD53 and gave a new message type ZORDERS and it is asking for with reference to message type...I am not able to see orders there.
Can anyone suggest how to proceed here?Is it something that only master idoc can be reduced?Pls suggest.
Regards,
Jeyananth

If you've just tried to enter ORDERS in there, you would've seen this message:
"There is no data maintained in the reduction pool for message type ORDERS
Message no. B1121
Diagnosis
This transaction is used for maintaining and displaying reduced message types. In the standard not all message types can be reduced.
There is no data in the reduction tool for message type ORDERS.
Procedure
Use the transaction WE30 for maintaining and displaying the associated intermediate document type, or use the transaction BD60 to maintain the data for the reduction tool."
But I wouldn't recommend reducing the IDoc - it's more trouble than it's worth IMHO.

Sendind idoc tcode foe msg type WVINVE and WPUUMS

Dear All,
What is the tcode for sending phy inventory data through IDOC message typy WVINVE, and also for message type WPUUMS POS interface: Upload sales data (Compressed)
Ex: BD10 for sending material.
Thanks and regards,
Arun.

Hi,
Wpuums is inbound IDOC so you can crete this IDOC with the help of We19
and for testing purpoase u can use WPUK tcode
Thanks
Amit Shivhare

Problem using IDOC_INPUT_DELVRY in ship.conf for msg type SHPCON

Hi Experts,
We are confirming the picked quantity from warehouse for the outbound delivery using the EDI IDOC_INPUT_DELVRY as shipping confirmation using message type SHPCON and process code DELV.
           Problem is that this process is checking the determination of the output type LAVA maintained in NACE before the actual post goods issue take place. since the SAP itself has the requirement check for goods issue status 'C' ( Complete check status ), this output type is not picked while doing the automatic post goods issue using EDI since at that time goods issue status is 'A'. In other words, goods issue has not taken place.
       But when we did manually using VL02N for confirmed picked quantity and did the post goods issue manually it is determining the output type LAVA since while checking the requirement in LAVA has goods issue status 'C' ( Completed ).
In simple words, while doing manually the output type LAVA is determined but while doing
automatic post goods issue using EDI output type LAVA is not determined.
This is very urgent. Please help with this?.
Thanks,
suresh

Hello Mohanaselvan,
Thank you for this info. Definitely making some progress now.
Can you advise some of the necessary iDOC DELVRY03 data elements necessary to transmit the sales order data?
I am receiving the 51 status error message:
"Data of Preceding Document was not transmitted" and
"Essential transfer parameters are missing"
I tried referencing the Sales Order in few places, but I don't seem to have it correct:
E1EDL20-VBELN = Sales Order (Instead of Delivery Number)
AT ITEM LEVEL
E1EDL43-QUALF=C
E1EDL43-BELNR=Sales Order
E1EDL43-POSNR=Sales Order Item Number
Regards,
Sandy

Idoc generation for message types

Hi All,
regarding IDOC generation....
how do we activate the message type so that every time the application data which is created or changed or deleted generates the idoc and send it to other system. If iam not using Chnage pointers technique then i would not be activating the message type in BD50. In such case ie if the message type is not present in BD50 list and if change pointers is not used to transfer that message type . How do we genrate the idoc for such message types.
Thanks
Avinash

Hi,
For ur scenario u need to go for change pointers method only.U have other options like distributing master data and transactional data..But i don't think anything otherthan change pointers is useful.
Regards,
Nagaraj

IDOC Exit for Basic Type PORDCR101

I had extended the idoc type PORDCR101( Create Purchase Order ) and added the new segment under E1BPMEPOITEM .
Now i want to find the exit which will help me in populating the added segment fields when the IDOC is posted .
Any sort of help is appreciated .
Regards,
Praveen.

Hello,
The message PORDCR will use FM IDOC_INPUT_PORDCR and further processing is done using a BAPI: BAPI_PO_CREATE.
Enhancement SAPLMEWP deals with the Exits related to the BAPI.
Hope the above point helps you.
Best Regards, Murugesh AS

Problem with HRMD_A06 IDoc and HRMD_A msg. type

Hi All,
When we are transferring data from r/3 to r/3 systems... 0001 info type is not getting filled. All other data is getting posted successfully.
The segments itself are not getting filled.
Can any one help me in this regard.

- Im assuming you have distribution model with message type HRMD_A06
- You also schedule the change pointer job ( BD21) for HRMD_A.
-You also have WE20 ( partner profile with message )
-you also have port
-When youre making change in IT0001 , youre saying nothing is happening?
Please check the above thing and let me know...
Thanks
Saquib

Duplicate IDOC created for basic type PEXR2002

Hi,
We are using PEXR2002 idoc for some document postings in FI. For a segment EIEDP02, when trying to write a BELNR field value which exceeds its size of CHAR 35. Its creating a duplicate segment with same key value. Because of this, the idoc not getting created and ends up in error.
Could you please anyone help me in this regard?
Thanks and Regards,
Vimala P

Hi,
In our process, the EIEDP02-BELNR value is actually filled with document text field value which is of length more than 35. What is happening right now is, if the length of document text having more than 35 characters and then with first 35 character of BELNR value one segment is created. And it again create one more segment EIEDP02 with BELNR value having the rest of the fields value(>35 characters). Thus creates duplicate segments which results in IDOC creation failure
Thanks and Regards,
Vimala P

HR IDOCS failing for Info Type 1002

Guys, I am moving from business side of SRM to techno/functional. We have HR data replication IDOCS failing from R/3 to SRM with the following error. Any help on how to debug this further and your thoughts/experience on this error
Error: insertion of infotype 1002 (return code 3 )
Message no. 5-133
Diagnosis
An error occurred when you tried to insert infotype 1002 using RH_INSERT_INFTY (return Code 3).
Thanks

Hi
This is a system bug.
Please go through the following SAP OSS Notes, depending on your SAP version/Support pack ->
Note 185422 HR-CA-ALE: Error with RH_INSERT_INFTY
Note 890704 RH_INSERT_INFTY: Inserting in the structural authorization
Note 832395 HRALX: Status 51: Insertion of infotype 1001
Note 766882 HRALX: Error when inserting infotypes
Note 850259 HRALX: Position deleted or not changed
Note 445336 Different ADATANR for to and from relationships
Note 532675 Interface correction for RH_OBJID_REQUEST and RHP_CRMQ
Note 451578 Error in module BBP_UPDATE_ORG_ADDRESS
Note 440135 Short dump NO_AUTHORIZATION when creating HR work center
Hope this will help. Do let me know.
Regards
- Atul

Idoc Reduction CREMAS

Hi,
Is there an alternative to this approach :
Problem: I create Vendor master idoc using basic type crema04 and message type cremas. Idoc reduction is present for this message type, so when the idoc is created only mandatory segment gets populated.
Solution I tried : Through BD53 , create a ZCREMAS reduction message type , select the segments to be populated , enable them and activate them . Use this message type for the generation of the idoc.
Question : Is there any alternative way to this method or this is the only way we can remove the idoc reduction for messag types?????
Thanks ,

Hi,
Perhaps you can use this custom exit '001' in include in include program <b>LBD11F0Q</b> to filter IDoc segment.
CALL CUSTOMER-FUNCTION '001'
    EXPORTING
       idoc_control_in = pxf_idoc_control
       target_idoc_type = target_idoctp
       target_cim_type = target_cimtyp
    IMPORTING
*      idoc_control_out = pxf_idoc_control
       idoc_control_out = idoc_control_out
    TABLES
       idoc_data        = pxt_idoc_data
       idoc_status      = t_idoc_status.
This is being in FM <b>MASTER_IDOC_DISTRIBUTE</b>.
For SAP best practise, i would suggest to use reduce message type or segment filter.
Again, hope this will help.
Regards,
Ferry Lianto

IDOC reduction for MSG type MATMAS

Similar Messages

Maybe you are looking for