Object type not maintained for message type

Hi,
I am working on chnage pointers for Vendor classification data. when I execute the program RBDMIDOC (BD21) I get the error Object type LIFNR not maintained for Message type.
If anyone has worked on change pointers, please guide me in solving this error.
Thanks
Hari

Hi
Which msg type u r using there.
Regads,
Prasad.

Similar Messages

Error inALE service (Segment type not maintained in Message type) status:29

Hi all,
Need your help.
I have a added the a segment to the message type and which is linked in WE82( Message type:Debmas,basic type:debmas06 and extensionZxxx). And the segment is also set for release.It is an outbound senario. When i process it manually in WE19 using the basic type with the enhancement and via message type (with the message type and the extended type) I can process the idoc and the segment whic i have added with the following fields are displayed. But when i post the customer in BD12 with the message type I am getting the error in BD87 as " error in ale service Segment type ZXXX does not exist in message type DEBMAS".
PLease do the needful. Its since 2 days I am struck with the same and was trying but I could not get any. Hope you guys might help me.
Anything else to be refreshed or anything else to be done except we31.we30, we81
Thanks in advance.
Edited by: Farhy Farhy on Aug 2, 2010 12:29 PM

Thanks for your reply Mr. Das.
I have tried all the things and did not find any solution..
Posted after checking all the things and the procedure. I did not write any custom program. Earlier I created the extension type and deleted and created the new extension type. But now it is taking the same old extension type and giving the error as the extension type is not maintained in the message type.
I have deleted the old extension type completely but the old is onle getting reflected. Anything to be done to refresh.
Waiting for the reply.

Custom segment does not exist for message type Debmas_cfs

Hi,
I have created a custom segment YEXTRA for basic type DEBMAS06.
I have done the configuration in We82 and We20.
I have implemented the segment in User Exit "EXIT_SAPLVV01_001". Now when I am executing the TCODE BD12 then it is creating the Idoc with custom segment. But when I apply the filter on sales org in BD64 then it starts giving me error that " Segment Y**** does not exist for message type DEBMAS_CFS.
Kindly suggest if I need to do some other configuration also.
Thanks.
Regards,
SAurabh

Hi Gearge,
To add custom segments, you should create an extension.
the TCODE is we30.
Refer this link:
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm
Regards,
Ravi

ERROR: "The IDoc interface is not complete for message type DELINF"

Dear All,
The ERROR happens when I use IDoc inbound test tool:
- Basic type used: DELVRY06
- Basicallly this IDoc is supposed to create inbound PGI of a DO. I just put the DO number in WE19.
But ended up with the error mentioned. Let me know if oyu need more details.
Thanks and regards,
Will.

Hi,
Please check whether the partner profile configuration is done completely such as any message control parameters are fine or not.
Regards
Archanaa

Number Range Object For following object is not maintained for year 2008,

Hello Together,
Now the 2008 year has begun.....All the number range object in Excise related process ( CIN ) has to be changed.
I would like to know whether i need to change the only Year in SNRO or i have add new year in that setting.
Below is the example :-
Ranges Year From Number TO Number Current Number
01 2007 001000000 99999999 10001013
If i change only year i,e. insted of 2007 i will change 2008....what will be impact?
Please guide
Thanks in advance
Shailesh

go to J1I9-select the object--here maintain a new year for the same number range:
Ranges Year From Number TO Number Current Number
01 2007 001000000 99999999 10001013
01 2008 001000000 99999999
give enter---save.
regards,
indranil

Archiving of ERS messages: maintain archiving parameters for message type

Dear experts,
I have problems creating archive messages for ERS messages in ECC 6.0. I always get message "Maintain archiving parameter(s) for output type ERS (appl. MR)" even if I have done all steps as described in SAP note 391822:
NACE: application "MR", output type "ERS"
details: storage mode "2 Archive only", document type "ZUNSGUTHCD"
processing routine: medium "1 print", program "RM08NAST", form routine "ENTRY_ERS", form "MR_PRINT".
A condition record for message type ERS is existing with function "VN" and medium "1" and date/time "4".
OAC2: document type "ZUNSGUTHCD", document class "PDF", status "x".
OAC3: object type "BUS2081", Doc.type "ZUNSGUTHCD", L "x", Content rep. ID "K1", link "TOA01", retention period "0".
The archive "K1" is existing and working for other documents, but not for ERS.
Something is missing, but I don't find out what. Any help is greatly appreciated, point are given!
Regards, Karsten

Dear experts,
I have problems creating archive messages for ERS messages in ECC 6.0. I always get message "Maintain archiving parameter(s) for output type ERS (appl. MR)" even if I have done all steps as described in SAP note 391822:
NACE: application "MR", output type "ERS"
details: storage mode "2 Archive only", document type "ZUNSGUTHCD"
processing routine: medium "1 print", program "RM08NAST", form routine "ENTRY_ERS", form "MR_PRINT".
A condition record for message type ERS is existing with function "VN" and medium "1" and date/time "4".
OAC2: document type "ZUNSGUTHCD", document class "PDF", status "x".
OAC3: object type "BUS2081", Doc.type "ZUNSGUTHCD", L "x", Content rep. ID "K1", link "TOA01", retention period "0".
The archive "K1" is existing and working for other documents, but not for ERS.
Something is missing, but I don't find out what. Any help is greatly appreciated, point are given!
Regards, Karsten

Error message "Data cannot be maintained for set type COMM_PR_PUR_1

Hi
While replicating the material master through R3AS I am getting an error for which the details to be checked in SMW01. In SMW01 when I selected the record for error details I am getting above error message. How to resolve ? Pls guide me stepwise. For your information I has cleared SMQ1 in R3 & SMQ2 in SRM
For curioisity next I selected all such error logs & deleted. It gave me one warning (some inconstinecies error) which I ignored. After that I checked SMQ1 of R3 & SMQ2 of SRM. No log
But I observed a strange thing. Whatever material codes I am creating it is going straightway to SRM without running R3AS transaction. I checked R3AM1, selected the row and cancelled. But still going without any interferrance. Why ? How shall I stop this.
Thanks

Hello,
>
BNR wrote:
> Hi
> While replicating the material master through R3AS I am getting an error for which the details to be checked in SMW01. In SMW01 when I selected the record for error details I am getting above error message. How to resolve ? Pls guide me stepwise. For your information I has cleared SMQ1 in R3 & SMQ2 in SRM
>(...)
Have a look at OSS note 1049693 - Data cannot be maintained for set type COMM_PR_PUR_1.
Regards.
Laurent.

Could not determine recipients for message type HRMD_B

Hi,
I am getting below Error in SRM when transferring Org Structure data from HCM system to SRM system in a Idoc. I am using Message type HRMD_ABA and not HRMD_B. I didn't maintain Distribution model for HRMD_B. But in my IDOC status I am seeing below error message for Message type HRMD_ABA Inbound to SRM.
Only I am seeing HRMD_B message type in transactions WE81 and WE82.
Any idea? I appreciate your help.
Could not determine recipients for message type HRMD_B
Message no. B1003
Diagnosis
An IDoc of message type HRMD_B was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
Thanks,
Shears

Hi Shears
Did you find soulution to your issue ??
thanks
Anup

Error in ALE service 29 Could not determine recipients for message type MAT

Hi Experts,
While transferring the material using ALE am getting error 29 ie 'Error in ALE service' and message is 'Could not determine recipients for message type MATFET'.
Also i ve recieved the materials with the proper status al the end am getting the above error.
Kindly help me out.
Thanks in advance.

Hi ,
Status 29 means " partner profile not found " . Please check if the recieving partner is configured properly in WE20 in sender system.
Also make sure that the Port and RFC definations are also completed. If the IDoc is manually triggered then please make sure that control record parameters of the idoc are properly filled - if we miss the details ( like wrong port given , wrong basic type for message type - or extended message type ) then also the idoc will fail in status 29 even though the partner profile is properly configured .
Since your idoc is getting generated i think no issues with BD64 since already interested recipeints were populated in control record of idoc.
Regards
Vikas Chaudhary

CONTROL DATA FOR ACTIVITY TYPE NOT MAINTAINED

dear all
i get this error when calculating production order cost
control data for activity type 1000\4230\1420 not maintained for fiscal year 2007
i hv maintained data in kp26
can any one pl help. i am learnign sap pp and hv 4.7 version
thanks and regards

Dear Anshuman
my prob. started during cost cal. in prod. order first error was version 0 not maintained for fiscal year 2007, THEN i maintained it in the path as told by you T code OKEQ.
but after that error changed to CONTROL DATA FOR ACTIVITY TYPE NOT MAINTAINED ( 1000/4230/1420)
i maintained data in kp26, but the error is still coming
pl. suggest some solution as i am not able to proceed further.
Thanks and regards
Raj

Can not generate one xsd file for message type in xi

Dear Experts.
I am not able to generate one XSD file from message type from XI 3.0, When i select message type and go to XSD tab then click on export xsd to file, it is generating two xsd files MainSchema.xsd, Schema1.xsd into one zip file, but i need only one xsd file to import it into MDM.
Could you please help
Thanks and Regards.
Sravya.
The following are the two files. MainSchema.xsd, Schema1.xsd .

Hi Harsha,
Thanks lot for the immediate response. Appreciate it.
Now I am able to generate the one xsd with your inputs , but i am not able to load it into mdm with out any changes in the generated XSD from Message Type. the below is only the original root tag, where modification required.
Original Element : MDM_CUST_MASTER_FILE_REQUEST_MT
==============
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:abc.com:MDM_Customer_Master_ECC" targetNamespace="urn:abc.com:MDM_Customer_Master_ECC">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
etc.
Case :.When i modify the above element as below with out xmlns, targetNamespace
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
I can import xsd into mdm with the above modification.
The generated XML out put File from mdm is having message type tag like below
?xml version="1.0" encoding="UTF-8"?>
<MDM_CUST_MASTER_FILE_REQUEST_MT>
<CUSTOMER> </customer> ...
note: no namespace for message type
Result:
1.When i send this xml file into XI it is failing in message mapping because it doesn't have namespace attached to it and failing in message mapping.
Finally i need your help to generate the xsd or data file like below to avoid mapping problem in xi.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MDM_CUST_MASTER_FILE_REQUEST_MT xmlns:ns0=urn:abc.com:MDM_Customer_Master_ECC>
Appreciate your help.
Thanks and Regards.
Sravya.

Output message type not triggered for few POs

---PRs got created manually. then PRs converted into POs through background job (me59n).
( 25 PRs got created manually with same vendor and pur.org combination then all PRs converted into POs through ME59N. In that 20 PRs had message type automatically but remaining POs haven't got the message type )
Condition record exists with vendor/pur.org combination.
and all IMG settings are correct.
medium is 8 (special function).
and not able to replicate the issue in quality systems.
Please Advise.
Thanks in advance.

PRs will not get any message type, POs will get a message record.
How is the situation now?
Did you get 20 POs only, or do you have 25 POs where just 20 have a message record?
In the first case convert the PR manually to a PO manually and see if you get a message record. You should not enter anything manually, it is supposed to work without entering anything manually because it was meant for auto PO. In case you have to enter anything manually, then this might be an indicator why auto PO could not work.
if the latter case, then compare a PO with and without message record on the fields that should match with your condition record.
Do you expect the same message type for all POs, are they all in the same purchasing organisation?
Read and check what is mentioned in KBA 1829682 - Output type is not determined in Purchase order

Message no. B1003""Could not determine recipients for message type ACPJMM""

Hi All,
While posting GR in MIGO, an error is showing. I am attaching the error description.
""Could not determine recipients for message type ACPJMM""
Message no. B1003
Diagnosis
An IDoc of message type ACPJMM was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
Yesterday it was not coming and GR was getting posted.. I was doing configurations for CIN and day before yesterday everything was done,all the registers were getting updated. For that I did many customisation in SPRO. I did settings in tax ion goods monement. and in Material master to assign screen sequence for foreign trade data screen. Is any customozation triggerring IDoc? Earlier also this came, that time we got client copy, but the problem is recurring. Its very urgent as we are going to transport SPRO settings to production.
Solutions will be rewarded.
regards
B Shar
Edited by: Ian Wong on Jul 4, 2008 4:48 PM

Hi
If you are not working with ALE & this message comes, then somone has mistakenly activated ALE linkages for IDoc Output in Accounting.
if you want to keep this active & go forward, you need to complete the Distribution model customizng in BD64.
Thanks & Regards
Kishore

Error In MIGO "Could not determine recipients for message type ACPJMM"

Dear all,
At the time of transaction Goods Receipt(MIGO), I am getting the error message "Could not determine recipients for message type ACPJMM".
System Diagnosis is as below
An IDoc of message type ACPJMM was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type
I have check the ALE Settings in we20 and we21
and have assigned the following message types under Logical syste Partner Type
Outbound
ACPJMM
MATMAS
MBGMCR
RSINFO
RSSEND
WHSORD
Inbound
ACPJMM
DEBMAS
FTDABA
FTDACO
FTDACU
INSPECTIONPLAN_CREATE
MATMAS
MBGMCR
RSRQST
WHSCON
I have also created and Assigned a Logical System to the client and have also created a RFC with the same name
I have checked all settings is SALE and they are Fine.
This is a single system
Please help this is really ugrent
Regards
Suhail John

Hi,
Goto table TRWCA (T Code SE30) and deselect all the checked entries.
This should solve your problem.
Regards,
Priyadarshi

Distibution Model- Outbound parameters for message type could not be found

Hi SRM Gurus,
Have you ever encountered this error while buidling Distribution model in BD64 -
When I try to generate partner profile, I am getting this error-
Outbound parameters for message type BBPCO BBPCO01 could not be created
Partner not found in partner table
This error is occuring for all message types.
Please let me know the solution if anyone has encountered this error before.
Thanks & Regards
Kapil

Hi
Are you geting this error while generate partner profile?
hope your sender and receiver logical system are correct.double check.
VERSION 3
OUTPUT MODE - tRANSFER idoc immediately option
connectivity between both sytems are ok.
did you save modelview ?
now ports automatically created . check we21 ,we20..
check your sm59 rfc destination? what type connection you made ? hope you maynot do mistake. howevercheck itup.
ask basis consultant assistance why ports anot genrated for backend system after you executed
tbd05 - do yo have entry ?
regards
muthu

Object type not maintained for message type

Similar Messages

Maybe you are looking for