Inspection method error in Ale

Dear All,
I am use ALE idoc to transfer inspection plan fron one client to another.
While sending inspection plan i am getting an error that no valied version of inspection method found.
But when i have checked this inspection metod , it is there with released version.
For one material plan get uploaded with this inspection method but gives error for another material inspection plan for same method
regards
Edited by: amol shahane on May 26, 2009 11:51 AM

Hi amol
use ALE idoc to transfer inspection plan fron one client to another.
While sending inspection plan i am getting an error that no valied version of inspection method found
Check the date of Creation of Version of Inspection Method that you are trnasfering.This must be prior to that of Creation of inspection plan.
For one material plan get uploaded with this inspection method but gives error for another material inspection plan for same method
check the valide from date of this Inspection plan in MAPL
for said material plan it must be prior.
Regards
Sujit S Gujar

Similar Messages

DMS: Objectlink to more than 50 inspection methods(QMBDOC) gives dump

Dear All,
I have a requirement of attaching more than 50 objectlink for inspection methods to one document info records.
So when i attach 40 to 50 inspection methds by BDC program or manualy & then i again try to attach one more inpection method object by clicking on F4 it gives a Runtime error RAISE_EXPECTION
Short Text: Exception condition "INVALID_DYNPROFIELD" raised.
A RAISE statement in the program "SAPLSHL2" raised the exception
condition "INVALID_DYNPROFIELD".
Since the exception was not intercepted by a superior
program, processing was terminated.
Is there any note to be applied for this.
I got a note:896655, which says i can attach upto 100 object links to a DIR, but this is giving a error after 40-50 object links when ever i click F4 for attaching more.if i manually put value in the inspection method name it takes it & also saves it.
Please advice.
Regards
Nishant..

Dear Nishant,
please check if the notes 880077 and 885977 are implemented. These notes solve several object link related issues too.
Further please check the settings for object links in your customizing.
First of of it is necessary to maintain the correct screen numbers for all needed objects within the customizing. Therefore go to transaction SPRO and select
Cross-Application Components
> Document Management
      > Control Data
          > Maintain Screen for Object Link
Here you can enter all needed SAP objects with the name and
the related screen number. If you do not know the object or the screen number you can display a list of all SAP standard objects in transaction SE80 under function group CV130 ("Screens").
So for material master you maintain the following entry:
SAP object    Screen    Description    Auth.
MARA            201      material master      1
Please note that the system automatically adds the leading "1" which is displayed in function group CV130 under
"Screens". So for object MARA you just have to enter 201 instead of 1201.
The value "1" in the column "Auth." is necessary to grant that always the latest dynpros and authorizations were used when linking this object to an document info record. This will avoid different problems by displaying linked documents from the object side.
The next step is to decide which objects should be used in the different document types. Therefore please go to transaction DC10 and choose the relevant document type. Afterwards please select "Define object links". Here you can
add all needed objects only by entering the object. The correct screen number is taken automatically. Also note the blue information buttons in the upper right corner which contain further necessary informations about the possible settings of the current screen.
After doing these settings in customizing you should be able to link the maintained objects to document info records and oppositely.
Important notes regarding the object link functionalities are:
880077: Performance problem using object links
885977: Extension to note 867241 on object links
926060: Extension of note 885977 for object link Purchase Order
960202: Object Links Deleted While Adding New Objects
1002648: Wrong behaviour while using RFC_CHANGE_DOCUMENT_MASTER
Best regards,
Christoph

Urgent :Getting error "No ALE scenario active in Profit Center Accounting"

Hi Experts
I am working on a LSWM project ,which uses BAPI BAPI_PROFITCENTER_CREATE for upload of data,but I am facing a strange problem during the IDOC posting the error "No ALE scenario active in Profit Center Accounting" is shown and the status of IDOC goes to 51.
I have done all the ALE setting required for LSMW like File port ,partner type and partner number.
Please help me to solve this error.
Thanks
-Mitesh
Message was edited by:
 Mitesh Parekh

Hi,
Refer This SDN Blog, which gives you steps in detail....
LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
 Most of the functions are within R/3, hence platform independence.
 Quality and data consistency due to standard import techniques.
 Data mapping and conversion rules are reusable across projects.
 A variety of technical possibilities of data conversion.
 Generation of the conversion program on the basis of defined rules
 Interface for data in spreadsheet format.
 Creation of data migration objects on the basis of recorded transactions.
 Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
 o If no standard programs available
 o To reduce number of target fields.
 o Only for fixed screen sequence.
 BAPI
 IDOC
 o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
 Choose settings -> IDOC inbound processing in LSMW
 Set up File port for file transfer, create port using WE21.
 Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
 Setup partner type (SAP recommended US) using WE44.
 Maintain partner number using WE20.
 Activate IDOC inbound processing.
 Verify workflow customizing.
Steps in creating LSMW Project:
 Maintain attributes choose the import method.
 Maintain source structure/s with or without hierarchical relations. (Header, Detail)
 Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
 Fields can be maintained individually or in table form or copy from other sources using upload from a text file
 Maintain relationship between source and target structures.
 Maintain Field mapping and conversion rules
 For each Target field the following information is displayed:
 o Field description
 o Assigned source fields (if any)
 o Rule type (fixed value, translation etc.)
 o Coding.
 o Some fields are preset by the system & are marked with Default setting.
 Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
 Specify Files
 o Legacy data location on PC / application server
 o File for read data ( extension .lsm.read)
 o File for converted data (extension .lsm.conv)
 Assign Files to defined source structures
 Read data Can process all the data or part of data by specifying from / to transaction numbers.
 Display read data To verify the input data being read
 Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
 Display converted data To verify the converted data
Import Data Based on the object type selected
 Standard Batch input or Recording
 o Generate Batch input session
 o Run Batch input session
 Standard Direct input session
 o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
 IDOC creation
 o Information packages from the converted data are stored on R/3 Database.
 o system assigns a number to every IDOC.
 o The file of converted data is deleted.
 IDOC processing
 o IDOCS created are posted to the corresponding application program.
 o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
 R/3 Transport system
 o Extras ->Create change request
 o Change request can be exported/imported using CTS
 Export Project
 o Select / Deselect part / entire project & export to another R/3 system
 Import Project
 o Exported mapping / rules can be imported through PC file
 o Existing Project data gets overwritten
 o Prevent overwriting by using
 Import under different name
 Presetting for Inbound IDOC processing not transportable.
One Last thing, Check in BD64 is the Distribution model is Active for Profit Center.
Cheers...
Santosh.D
Mark All the Usefull Answers.

Inspection Method (Quality Configuration)

Hi,
I have created a new Plant. Created the Material Specification Characteristics (T Code: QS21).
While creating the Inspection Plan (T Code: QP01), the system throw an error saying 'METHOD INSDUMMY, VERSION, Plant 1100 is not available.
When I cross-checked with old Plants, the Inspection Method INSDUMMY is assigned with the all old Plants.
Pls. tell me from where I can assign the same.
Regards,
P K Karn

PK Karn,
You need to create inspection method "INSDUMMY" using transaction "QS31" for plant 1100.
In the Initial screen you need to populate the plant and inspection method and key date from which this needs to be copied... so give the old plant referance which you were mentioning.
Now you will be able to assign the Inspection method to MIC.
Regards,
Prasobh

Error in ALE Service While Creation of Vendor Master

hi,
I am using a scenario where a third party system is sending vendor master data to a R/3 system The file is picked up by the file adapter(sender) and mapped to IDOC format, using Idoc adapter (receiver). A Vendor is then created by posting the CREMAS03 IDOC into the R/3 system.
Everything goes fine till the Idoc comes into the R/3 system. There in BD87(Idoc Status Monitor), getting the "Error in ALE Service" error. When expanded further the specific error is that of "Cross-system company code xxxx does not exist". What is generally the cause of this error and how would I resolve it?
For those of you who have attended TBIT 40, this scenario is Example 1 - Creation of Vendor Master Data.
Any help would be appreciated?
regards,
SK

one more thing
if you want to be sure that you're using the right data
try to set your system to send the vendor data out
first - send it from BD14
and then you'll know which fields do you need
if you do that take a look at segment E1LFB1M
and check for BURKS
Regards,
michal

No such method error when launching the Interactive form

Hi Experts,
I have developed a simeple Java Webdynpro application and added an Interactive form without any controls in it. Created the context with one value node and a binary value attribute.
I have assigned value node to datasource and binary attribute to pdfSource. When I launch the application I am getting the following no such method error.
java.lang.NoSuchMethodError: com/sap/tc/webdynpro/clientserver/uielib/adobe/api/IWDInteractiveForm.setTemplateSource(Ljava/lang/String;)V
The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.
If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.
My NWDS is of Version 7.0.06
and J2EE Engine is of Version 6.40.
any guess why I am getting this error.
Thanks
Chinna.

Issue solved. Compatablility issue NWDS 2.0 Version should use for NW 2004.

Status record 65 error in ale service

HI Experts,
               I have an issue when I tried to send a cost center idoc from one system to another. The company code for the record is 0093 in the sender system; however when the idoc gets created, in the idoc the value of the company code becomes SAH001. I dont know why this happens.
This is the record to in the corresponing table table- which is to be sent from sender to Receiver. The company code ie company code field value is 0093 .
The RFC/LS connections have been done and checked. I am able to send the cost center group data correctly. While sending the cost center I am encountering the following error:-
For an example
Content of created Idoc in sender
Company code field |   SAH001
The company code info is now SAH001. I wonder why ?
So when we send the idoc to recceiver, we get the same company code and I get an error that company code doesnt exist.
Content of idoc in receiver
Company code field |   SAH001
I want to display 0093.
Please tel me what is error and how to rectify?
Thanks & regards
Mathi

hI,
Testing inbound idoc :
Once you configured everything then goto WE19 Transaction :
Give message type or idoc type and execute .
now here you need to fill the Mandatory data in each segment,once you done then
idoc->edit control record -> here you need to fill sender and receiver details.
now you should get green color ,if you get red color then config issue.
now click on start inbound -> now you will get idoc number.
if you want to debug then click on inbound function module -> enter FM -> select call in debug mode and enter.
now cursor will go debug mode
http://www.photographybykevin.net/sap/idoc_overview.pdf
Testing Outbound idoc :
Once you done all configuration ..
Let me say example like invoice ,you need to send invoice from SAP R/3 to other system.
create invoice at VF01 -> Here customer should configure in Parter profile ,once you create invoice ,it creates the idoc.
debugging Outbound IDOC :
keep the break point in form routine above as i said
Create invoice or invoice list
when you maintain output type in invoice or invoice list -
Now click on Further data ->select peridoc scheduling-> back and save it.
Run RSNAST00 Program
Output application : V3
Object key : Invoice or invoice list number
Output type : RD00 or LR00
Medium = 6(EDI) ,A (ALE)
when you execute the program and it will goto debugging.
See the below status codes :
See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes
Successful Transmission:
03 - Successful outbound transmission
12 - Dispatch OK
IDoc being processed:
01 - IDoc created
30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)
ALE Error Messages:
02 - Error passing data to port
04 - Error within control information on EDI subsystem
05 - Error during translation
25 - Processing despite syntax errors (outbound)
29 - Error in ALE service
32 - Resubmit edited intermediate document (DO NOT USE)
Syntax Error Messages:
26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes
IDoc Processed Successfully:
50 - IDoc added
53 - Successful posting
IDoc ready for processing:
64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Errors in IDoc Processing:
51 - Error - application document not posted
56 - IDoc with errors added (You should never see this error code)
60 - Error during syntax check of IDoc (inbound)
61 - Processing despite syntax error (inbound)
63 - Error passing IDoc to application
65 - Error in ALE service - indicates partner profiles are incorrect
69 - IDoc was edited
Regards,
Nagaraj

IDOC: Error in ALE Service

Hi All,
I have created a new outbound idoc type ZSLSRPT and assigned it to a partner profile with type LI in we20. I tried running my customized program for idoc outbound and the status shows Error in ALE Service, Entry in outbound table not found.
Am I missing something with the partner definition? Do I need to configure the vendor output type in NACE? Please help.
Thanks,
Kenny

Hi Kenny,
Have you setup the distribution model (BD64) for the corresponding message type?
Also check this link for your reference.
http://help.sap.com/saphelp_nw04/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm
Regards,
Ferry Lianto

IDocStatus:Error in ALE service Cross-system company code does not exist

HI All,
I am sending CREMAS04 IDOC from XI to one R/3 system,and in R/3 a vendor should get created in master table.
My IDOC is getting posted successfully but in R/3 system I am getting error that
IDoc: 0000000000705816 Status: Error in ALE service
T100 Text: Cross-system company code XXX does not exist
I have created partner profiles in receiver system and in partner profiles I have set the process code as CRE1.
Please help me to resolve this problem.

Hi Shweta
Have you checked with the data i.e. company code .
May the company code which you are passing is not there in ur receiver system.
Just check it out.
Regards
-Mitesh

MM SUS Vendor Replication Error: Error in ALE Service

Dear Experts,
We are implementing MM SUS (SRM 5.0). As a part of this we need to replicate vendors from ECC to SUS system via XI. We have created a Reduced Message Type Z_CREMAS_SUSMM and had set up the partner profile in WE20 with SUS logical system as destination and specifing the Message Type, and port of the XI system
We executed the transaction BD14 for replication, it is resulting in error 29 : Error in ALE Service : Entry in Outbound table not found.
Please provide inputs to overcome this problem
Thank you,
Regards,
Ravi

Hi Ahmed,
Thanks for your reply. We have configured as per SAP configuration guide(plan driven procurement). As per this we had set up partner profile for SUS logical system and define the outbound parameters with receiver port of XI system.
If you feel one more partner profile need to be setup for XI system then please advise us for necessary configuration.
Thanks
Ravi

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

Error in ALE Service

hi
using the t.code BD13, i got the Customer Master Record in to the system
WE02 / WE05
IDoc:207013 Status: Error in ALE Service
Could not determine recipents for message type DEBFET
then i did in t.code WE19-- Function module IDOC_INPUT_DEBFET (in background)
Pop-up window
No Object for request IDoc selected for sending
Pop-up window
IDoc 207014 was saved and processed by function IDOC_INPUT_DEBFET
I cheked the status in WE02
IDoc:207014 Status: Application document not Posted
No Object for requested IDoc selected for sending
56 - EDI : Partner profile inbound not available.
please give me the solution, where i have to correct the issue
and i am not getting the function IDOC_INPUT_DEBITOR_MDM
Babu rao

in WE20, can yoy pls check if you have the partner profile maintained. If not pls maintain the same and the issue should be resolved.
Hope this helps.
rgds

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

Error in ALE service status 29

EXPERTS.
i have configurged all the ale settings.
1)logical systems   SALE
sender - 800 client
receiver-810 client
2) SM59 R/3 connections
   Receiver , here i checked the remote login , it is working , i mean i am able to login to 810 client
3)WE21 TRfc
generated port ie A000000038.
and given RFC destination as RECEIVER ---this is the logical system name of receiver
4)Done BD64
5)WE20 outbound partner profile
here in outbound parametes eneterd message type as cosmas
and in this given receiver port as A000000038.
and basic type as cosmas01.
6)Now i activated all the settings for changes pointers.
7)I changed cost centre in KS02 and saved
8)Executed BD21 ie idoc generation for change pointers
Got a pop up saying 1 master copy idoc generated , 1 communication idoc generated.
9)WE02.
Now status is 29 Error in ALE service
I clicked on control record.
In partner following information is there.
Receiver Informatiion
Port    : A0000000038
partner number : RECEIVER
partn type : LS
Sender Infornation
Port : SAPSHS
Partner number : SENDER
partn type : LS
In sender info port is comming as SAPSHS i dont know from where it is comming.
So please tell me , where went wrong.

Hi thanks for the reply
I executed WE19 as you said.
In the input screen given the idoc num 5234746
and in the menu option -> IDoc ->Test outbound idoc ->executed.
Now pop up came Idoc sent to R/3 sytem or external program.
Then we02.
one new idoc is generated ie 5234747.
And it is green ie status 3 data pased to port ok.
1) Why now it came to status 3? Even i checked the earlier failed idocs they also turened to status 3? Why so
2)So when ever we execute we19 , will it generate new idoc?
3)When we are doing in our company servers is it suggestable to execute we19 rather than BD87 , since WE19 geneates new idoc?Will business accepts it?

Vendor Master Replication Error from ECC to SUS : Error in ALE Service

Dear Experts,
We are implementing MM SUS (SRM 5.0). As a part of this we need to replicate vendors from ECC to SUS system via XI. We have created a Reduced Message Type Z_CREMAS_SUSMM and had set up the partner profile in WE20 with SUS logical system as destination and specifing the Message Type, and port of the XI system
We executed the transaction BD14 for replication, it is resulting in error 29 : Error in ALE Service : Entry in Outbound table not found.
Please provide inputs to overcome this problem
Thank you,
Regards,
Ravi

Hi,
Check
Re: Idoc Error Status "Entry in outbound table not found "
Looks like some issue with the partner profile set up for the sender or receiver of the EDI message in WE20.
Set up them again and When these have been set up try reprocessing your IDocs from BD87

Inspection method error in Ale

Similar Messages

Maybe you are looking for