SD: IDOC: Missing functions

Hi
I'm trying to send picking data via edi/ale to a non-SAP system.
I tried to add a process code to the message type PICKSD and only "SD02" are available? When i try to add any of the other codes i get a error when i try to use edi/ale. "EDI: Function module "ME_EDI_ORDCHG_ORD_ID01 "does not exist.
Is this normal? We are on Rel4.7

You need to two settings to resolve this issue in we42.
1)Goto we57 and make entry for idoc type/message type/function module
2)And go to BD51 and create entry for your function module.
Regds
Manohar

Similar Messages

Missing Functionality: Dunning Wizard - We need table CRD1

Hello,
Missing Functionality: Dunning Wizard - We need table CRD1 in the dunning PLD templates!!!
This Workaround is impossible.
As a workaround I suggest to store this information in the UDFs that you would create on the OCRD table that is exposed in the dunning PLD templates.

keine Antwort ist auch eine Antwort

MISSING FUNCTIONALITY-The field "VatIdUnCmp" is not exposed in DI API & DTW

The field "VatIdUnCmp" (Unified Federal Tax ID) is not exposed by the
DI API and therefore not available in DTW.
This is a missing functionality.
In order to have this non-legal requirement, as request in the note 1028874, I send this development request
Thanks for your cooperation.
Fabio Fambrini

Maybe check here:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c5f5dbcc-0a01-0010-5d82-f25f2bee715e
HTH,
Frank

Packaging data is not saved in document draft (missing functionality)

Dear all,
Packaging data, usually typed with delivery note, is not saved together with Delivery Note draft (No matter the draft is saved manually or automatically by approval procedure).
I have tested on SBO 2005B latest patch, 2007B latest patch, and 8.8 version, they all do not save packaging data in draft.
The draft related tables for packaging (DRF7, DRF8) are already existed in SBO, I encourage to get this missing functionality back.
My customers are highly needed for this function for better operation flow.
It would be appreciated if this request could be implemented in the near future patch.
Thanks in advance

Have also just discovered that this functionality is missing, although we were going to be using it when saving an AR Invoice as Draft. This is a major hole and is going to cause a big issue for a current implementation where this method was going to be used to create 'Split Deliveries' without making the account postings and allow Despatch paperwork for the Shipping company to be printed. The solution was going to be extremely simple, but now potentially is going to result in a substantial SDK development.
It would be useful to know whether there is any likelihood that it will be resolved in the near future, i.e. in a patch for 2007A SP1 or 8.8.

Mail for Exchange Missing Functions E71 v E72

Hi All,
So I have been using an E71 with Mail for Exhcange for some time now and find it is very good.
However
I have an E72 with Mail for Exhcange already installed on the device BUT it clearly has missing functions whihc I had on the previous version on Mail fo Exchangeo n the E71.
These are
Comp Directory - Very useful for looking up contacts details from the GAB
View Log in Mail for Exchange. This is useful to see what the error is for a reason why the device may not be syncing with the MS Exchange Server.
Full resync in mail for Exchange. This again useful for support as other users will tell you that if the two systems have got their wires twisted, a full resync can fix the problem!
What version of the software do I have? Helps for future support and upgrades.
So Mr Nokia Software Developer. When can we have these functions added? Do we have to drop this software tool and device....
MODERATOR'S NOTE:
We have edited your post. Please be advised that feedback on Nokia devices are accepted in the forum provided that they are written in an acceptable manner such as tone and the choice of words.

As far as the version number goes - it's not a misprint, it's just they way Nokia numbering scheme works. build 2.09 is version 2.9. Similarly in Nokia Maps build 3.04 is called version 3.4... go figure.
Lumia 920, Lumia 800
Nokia N8-00 (NAM, Product Code: 059C8T6), Symbian Belle, Type RM-596, 111.030.0609
Nokia 5800 XpressMusic (NAM, Product Code: 0577454) Software v51.2.007, Type RM-428

OWB bugs, missing functionality and the future of OWB

I'm working with OWB for some time now and there are a lot of rough edges to discover. Functionality and stability leave a lot to be desired. Here's a small and incomplete list of things that annoy me:
Some annoying OWB bugs (OWB 10g 10.1.0.2.0):
- The debugger doesn't display the output parameters of procedures called in pre-mapping processes (displays nothing, treats values as NULL). The mapping itself works fine though.
- When calling selfmade functions within an expression OWB precedes the function call with a constant "Functions." which prevents the function from being executed and results in an error message
- Occasionally OWB cannot open mappings and displays an error message (null pointer exception). In this case the mapping cannot be opened anymore.
- Occasionally when executing mappings OWB doesn't remember changes in mappings even when the changes were committed and deployed
- When using aggregators in mappings OWB scrambles the order of the output attributes
- The deployment of mappings sometimes doesn't work. After n retries it works without having changed anything in the mapping
- When recreating an external table directly after dropping the table OWB recreates the external table but always displays both an error message and a success message.
- In Key Lookups the screen always gets garbled when selecting an attribute as a join condition
- Usage of constants results in aborts in the debugger
- When you reconcile a table used in a key lookup the lookup condition sometimes changes. OWB seems to remember only the position of the lookup condition attribute but not the name.
- In the process of validating a mapping often changes in the mapping get lost and errors occur like 'Internal Errors' or 'Null Pointer Exceptions'.
- When you save the definition of external tables OWB always adds 2 whitespace columns to the beginning of all the lines following 'ORGANISATION EXTERNAL'. If you save a lot of external table definitions you get files with hundreds of leading whitespaces.
Poor or missing functionality:
- No logging on the level of single records possible. I'd like the possibility to see the status of each single record in each operator like using 'verbose data' in PowerCenter
- The order of the attributes cannot be changed. This really pisses me off expecially if operators like the aggregator scramble the order of attributes.
- No variables in expressions possible
- Almost unusable lookup functionality (no cascading lookups, no lookup overrides, no unconnected lookups, only equal condition in key lookups)
- No SQL overrides in soruces possible
- No mapplets, shared containers or any kind a reusable transformations
- No overview functionality for mappings. Often it's very hard to find a leftover operator in a big mapping.
- No copy function for attributes
- Printing functionality is completely useless
- No documentation functionality for mappings (reports)
- Debugger itself needs debugging
- It's very difficult to mark connections between attributes of different operations. It's almost impossible to mark a group of connections without marking connections you don't want to mark.
I really wonder which of the above bugs and mssing functionality 'Paris' will address. From what I read about 'Paris' not many if at all. If Oracle really wants to be a competitor (with regard to functionality) to Informatica, IBM/Ascential etc. they have a whole lot of work to do or purchase Informatica or another of the leading etl tool
vendors.
What do you think about OWB? Will it be a competitor for the leading etl tools or just a cheap database add on and become widely used like SAB BW not for reasons of technology or functionality but because it's cheap?
Looking forward to your opinions.
Jörg Menker

Thanks to you two for entertaining my thoughts so far. Let me respond to you latest comments.
Okay, lets not argue which one is better.. when a tool is there .. then there are some reasons to be there...But the points raised by Jorg and me are really very annoying. Overall I agree with both yours and Jorg's points (and I did not think it was an argument...merely sharing our observations with each other (;^)
The OWB tool is not as mature as Informatica. However, Informatica has no foothold in the database engine itself and as I mentioned earlier, is still "on the outside looking in..." The efficiency and power of set-based activity versus row-based activity is substantial.
Looking at it from another way lets take a look at Microstrategy as a way of observing a technical strategy for product development. Microstrategy focused on the internals (the engine) and developed it into the "heavy-lifting" tool in the industry. It did this primarily by leveraging the power of the backend...the database and the hosting server. For sheer brute force, it was champion of the day. It was less concerned with the pretty presentation and more concerned with getting the data out of the back-end so the user didn't have to sit there for a day and wait. Now they have begun to focus on the presentation part.
Likewise this seems to be the strategy that Oracle has used for OWB. It is designed around the database engine and leverages the power of the database to do its work. Informatica (probably because it needs to be all things to all people) has tended to view the technical offerings of the database engine as a secondary consideration in its architectural approach and has probably been forced to do so more now that Oracle has put themselves in direct competition with Informatica. To do otherwise would make their product too complex to maintain and more vendor-specific.
I am into the third data warehousing/data migration project and my previous two have been on Informatica (3 years on it).I respect your experience and your opinions...you are not a first timer. The tasks we have both had to solve and how we solved them with these tools are not necessarily the same. Could be similar in instances; could be quite different.
So the general tendency is to evaluate the tool and try to see how things that were needed to be done in my previous projects can be done with this tool. I am afraid to say .. I am still not sure how these can be implemented in OWB. The points raised by us are probably the fall out of this deficiency.One observation that I would make is that in my experience, calls to the procedural language in the database engine have tended to perform very poorly with Informatica. Informatica's scripting language is week. Therefore, if you do not have direct usability of a good, strong procedural language to tackle some complicated tasks, then you will be in a pickle when the solution is not well suited to a relational-based approach. Informatica wants you to do most things outside of the database (in the map primarily). It is how you implement the transformation logic. OWB is built entirely around the relational, procedural, and ETL components in the Oracle database engine. That is what the tool is all about.
If cost is the major factor for deciding a tool then OWB stands far ahead...Depends entirely on the client and the situation. I have implemented solutions for large companies and small companies. I don't use a table saw to cut cake and I don't use a pin knife to fall trees. Right tool for the right job.
...thats what most managers do .. without even looking how in turn by selecting such a tool they make the life tough for the developers.Been there many times. Few non-technical managers understand the process of tool evaluation and selection and the value a good process adds to the project. Nor do they understand the implications of making a bad choice (cost, productivity, maintainability).
The functionality of OWB stands way below Informatica.If you are primarily a GUI-based implementer that is true. However, I have often found that when I have been brought in to fix performance problems with Informatica implementations that the primary problem is usually with the way that the developer implemented it. Too often I have found that the developer understands how to implement logic in the GUI component (the Designer/Maps and Sessions) with a complete lack of understanding of how all this activity will impact load performance (they don't understand how the database engine works.) For example, a strong feature in Informatica is the ability to override the default SQL statement generated by Informatica. This was a smart design decision on Informatica's part. I have frequently had to go into the "code" and fix bad joins, split up complex operations, and rip out convoluted logic to get the maps to perform within a reasonable load window. Too often these developers are only viewing the problem through the "window" of the tool. They are not stepping back and look at the problem in the context of the overall architecture. In part Informatica forces them to do this. Another possible factor is they probably don't know better.
"One tool...one solution"
Microstrategy until recently had been suffering from that same condition of not allowing the developer to create the actual query). OWB engineers need to rethink their strategy on overriding the SQL.
The functionality of OWB stands way below Informatica.In some ways yes. If you do a head-to-head comparison of the GUI then yes. In other ways OWB is better (Informatica does not measure up when you compare it with all of the architectural features that the Oracle database engine offers). They need to fix the bugs and annoyances though.
.. but even the GUI of Informatica is better than OWB and gives the developer some satisfaction of working in it.Believe me I feel your pain. On the other hand, I have suffered from Informatica bugs. Ever do a port from one database eingine to another just to have it convert everything into multi-byte? Ever have it re-define your maps to parallel processing threads when you didn't ask it to?
Looking at the technical side of things I can give you one fine example ... there is no function in Oracle doing to_integer (to_number is there) but Informatica does that ... Hmm-m-m...sorry, I don't get the point.
The style of ETL approach of Informatica is far more appealing.I find it unnecessarily over-engineered.
OWB has two advantages : It is basically free of cost and it has a big brother in Oracle.
It is basically free of cost...When you are another "Microsoft", you can throw your weight around. The message for Informatica is "don't bite the hand that feeds you." Bad decisions at the top.
Regards,
Dan Phillips

Missing Function Modules - EWA_MAIN_BUSINESS_HOURS & READ_STAMP

Hi Gurus,
When i am generating EWA for system in Solution Manager, i am getting the error
under Service Preparation
- Missing Function Modules
1. EWA_MAIN_BUSINESS_HOURS
2. READ_STAMP
*In the satellite system,tcode-sdccn*
Below are the errors:
1) EWA_MAIN_BUSINESS_HOURS : no matching interface found
function module not found
EWA_MAIN_BUSINESS_HOURS : funcname /SDF/MAIN_BUSINESS_HOURS , module 000156
2) READ_RFC_LIST : # of imp params in funcmod < # of imp params in mod 000152
READ_RFC_LIST : inconsistency in # of imp params found for mod 000152
READ_RFC_LIST : non-default imp param IF_ANONYMIZE is not passed to mod 000152
READ_STAMP : no matching interface found
function module not found
READ_STAMP : funcname /BDL/READ_STAMP , module 000153
Can Anybody help me to resolve this issue.
Regards,
Ashok

The modules EWA_MAIN_BUSINESS_HOURS, READ_STAMP and READ_RFC_LIST are supplied with the next version of ST-PI, which is currently scheduled to be released for customers on December 15. I can only ask you to ignore the error until after the next version of ST-PI has been installed on the system.
Please be informed that the errors are not critical and will disappear
by installing the latest ST-PI which will be release around december the
15th 2008.
Edited by: Felipe Pitta on Dec 2, 2008 12:22 PM

Need help for IDOC inbound function module !

Hi guys please help me to create a IDOC inbound function module.
What are the parameters and tables.
How to write the code.
What it does.
Please send me one inbound func module code if possuble
Thanks

Hi,
You need to create an inbound function module. Then define the process code in transaction we42 and attach the function module to this process code.
In the function module you create you need to define tables of types EDIDC (Control record (IDoc)), EDIDD (Data record (IDoc)) and BDIDOCSTAT (ALE IDoc status (subset of all IDoc status fields)).
Regards,
Soumya.

IDOC for Functional Areas

Hi,
I am looking for some IDOC for the creation of Functional Areas.
Transaction : FM_FUNCTION
Table : TFKB
I have not find any yet, do you know how can i fine the IDOC or maybe it does not exist any IDOC for Functional Areas?
Thank you,
Regards,
Zheng

As far as I know, there is no standard IDoc for it. However, to give you a pointer, you can look at FM FM_FUNC_AREA_CREATE or BUS0023 (Functional Area).
Thanks & regards,
Hadiman

Making Custom Idoc Script function

Hi all,
I am making a custom Idoc Script function. I have merged the resource
table into the core IdocScriptExtensions table. But i am not able to call the custom function in SiteStudio. Find below the steps that i have taken
step1) I have added a resource (Static Table) in my component which merges to "IdocScriptExtensions" fucntion.
Step2) I have already created the java class.
Step3) Edited <td>Myname</td><td>Myclass</td><td>MyloadOrder</td> in the resource with corresponding values.
Step4) From component settings added the custom classes.
Step5) made a build of the component.
Step6) Installed the component in my server.
now when i go to SS Designer and call this function then no response is generated.
This component will return me a boolean by quering DB. I have number of sysouts and traces but none of them is printed on the console. Can somebody please provide insited into what probably might be amiss here.
ANY pointers will be hightly appriciated. waiting for a quick response.
reagrds,
sapan

Hi Sapan,
For the most part your steps look correct. Personally I would probably do the following:
1. move your component's classes folder back inside the component
2. register the folder in the component
3. add the folder to the class path
4. in the component's hda file, check to make sure there the merge rule is set for your IdocScriptExtensions entry.
if all of those are correct, occasionally the content server can be tempermental when new classes are added and so I would try disabling the component, restarting, then enabling and restarting.
If everything is compiled, it has to be either a classpath issue or an issue merging your IdocScriptExtensions table.
Also, if you go to Administration>Configuration Info, expand enabled components and find yours, it will tell your the classpath registered for your component(though your code is in the content server classes folder).
Sounds like you are really close though...did you get the debugger working?
David

Error message : Info Idoc missing ;database system

I am trying to load the data from database system oracle ,the data was successfully loaded into psa , but cant able to load the data into ods from psa .
Data in psa is all green without any errors , as info idocs are missing its not letting to load data manually from psa to ods ,
I try to reload but coming up with same error
Next day problem was fixed automatically, I want to know what is the exact reason for this problem and how can next day it fixed automatically

Error message : Info Idoc missing ;database system
I need the solution urgently, please help

Inbound IDoc Posting Function Module

Give me an example of   how to write "Inbound IDoc Posting Function Module".
In my IDOC i have 10 segments each containing 1 field.
How do i create the Inbound IDoc Posting Function Module ??
Is the following code correct ??
FUNCTION ZIDOC_INBOUND.
""Local interface:
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
*DATABASE TABLES
TABLES:LIKPUK.
*DATA DECLARATIONS
    DATA: SALES_ORDER_NUM             LIKE Z1VBELN.
    DATA: DEL_TYPE                    LIKE Z1LFART.
    DATA: ACTUAL_GOODS_MOVEMENT_DATE LIKE Z1WADAT_IST.
    DATA: SHIPPING_POINT              LIKE Z1VSTEL.
    DATA: LOADING_POINT               LIKE Z1LSTEL.
    DATA: ROUTE_PGI                   LIKE Z1ROUTE.
    DATA: PICK_DATA                   LIKE Z1KODAT.
    DATA: CUST_NO                     LIKE Z1KUNNR.
    DATA: LOCAL_DATE                  LIKE Z1STDAT.
    DATA: TOTAL_GOOD_MOV              LIKE Z1WBSTK.
*INTERNAL TABLE DECLARATION
DATA:
IT_LIKP LIKE LIKPUK OCCURS 0 WITH HEADER LINE.
INITIALIZE WORK FLOW
    WORK_RESULT = C_WF_RESULT_OK.
     LOOP AT IDOC_CONTRL.
MAKE SURE WE HAVE CORRECT MESSAGE TYPE PASSED.
     IF IDOC_CONTRL-MESTYP NE 'Z_IDOC_PGI'.
     RAISE WRONG_FUNCTION_CALLED.
     ENDIF.
CLEAR APPLICATION BUFFERS BEFORE READING NEW ENTRY
    CLEAR :IT_LIKP.
REFRESH IT_LIKP.
*PROCESS ALL THE DATA RECORDS IN AN IDOC AND TRANSFER THEM TO
*APPLICATION BUFFERS
INCLUDE MBDCONWF.
LOOP AT IDOC_DATA WHERE DOCNUM EQ idoc_contrl-docnum.
CASE IDOC_DATA-SEGNAM.
WHEN'Z1VBELN'.
   SALES_ORDER_NUM =    IDOC_DATA-SDATA.
   MOVE-CORRESPONDING SALES_ORDER_NUM TO IT_LIKP.
WHEN 'Z1LFART'.
   DEL_TYPE    = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING DEL_TYPE TO IT_LIKP.
WHEN 'Z1WADAT_IST'.
   ACTUAL_GOODS_MOVEMENT_DATE    = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING ACTUAL_GOODS_MOVEMENT_DATE TO IT_LIKP.
WHEN 'Z1VSTEL'.
   SHIPPING_POINT    = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING SHIPPING_POINT TO IT_LIKP.
WHEN 'Z1LSTEL'.
   LOADING_POINT   = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING LOADING_POINT TO IT_LIKP.
WHEN 'Z1ROUTE'.
   ROUTE_PGI    = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING ROUTE_PGI TO IT_LIKP.
WHEN 'Z1KODAT'.
   PICK_DATA =   IDOC_DATA-SDATA.
   MOVE-CORRESPONDING PICK_DATA TO IT_LIKP.
WHEN'Z1KUNNR'.
   CUST_NO =   IDOC_DATA-SDATA.
   MOVE-CORRESPONDING CUST_NO TO IT_LIKP.
WHEN'Z1STDAT'.
   LOCAL_DATE =   IDOC_DATA-SDATA.
   MOVE-CORRESPONDING LOCAL_DATE TO IT_LIKP.
WHEN'Z1WBSTK'.
   TOTAL_GOOD_MOV =   IDOC_DATA-SDATA.
   MOVE-CORRESPONDING TOTAL_GOOD_MOV TO IT_LIKP.
ENDCASE.
ENDLOOP.
selecting data from the database
select * from likp into corresponding fields of table it_likp.
add status record
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = it_likp-VBELN.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = it_likp-VBELN.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-LFART.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-LFART.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-WADAT_IST.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-WADAT_IST.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-VSTEL.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-VSTEL.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-LSTEL.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-LSTEL.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-ROUTE.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-ROUTE.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-KODAT.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-KODAT.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-KUNNR.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-KUNNR.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = SY-DATLO.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = SY-DATLO.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-WBSTK.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-WBSTK.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
endloop.
endfunction.

Hi,
First goto WE20-> click on the logical system , now select the receiver LS which you are using as your partner. Now in the inbound parameters cehck what is the process code is attached.
once you get the process code then go to WE42 tcode.. there you give the process code and then double click you will get the function module IDOC_INPUT_FIDCMT.
Hopw you got my point.
Regards,
Nagaraj

Idocs missing from source system

Hello,
I am trying to extract data from R3 to BW. I am getting an error message in BI, No idocs arrived from the source system.
In SM58 system showing the message 'No service for system SAPECC, CLIENT 800 IN INTEGRATION DIRECTORY'. Please help on this issue
Regards,
Ramesh

Hi Ramesh,
Check whether the connection is proper between BW & R/3.
Goto your Source system> Right clcik> Check.
You can also check the following :
No Idocs arrived from the source system.
Idocs missing: No selection information arrived from the source system
Error when updating Idocs in Source System
Hope it helps!
Regards,
Pavan

Creating a custom IDoc inbound function module

I have created a custom idoc.I wanted to create a custom IDoc inbound function module, this Function module will provide to launch a BAPI .Tell me how to "create" inbound function module for the custom idoc ?

Goto any standard for the Paramtetres
*" IMPORTING
*"     REFERENCE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     REFERENCE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     REFERENCE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     REFERENCE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     REFERENCE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     REFERENCE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*"     REFERENCE(DOCUMENT_NUMBER) LIKE VBAK-VBELN
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*"      EDI_TEXT STRUCTURE EDIORDTXT1 OPTIONAL
*"      EDI_TEXT_LINES STRUCTURE EDIORDTXT2 OPTIONAL
Do the below configs.
1.Recognise the funcmod as Inbound -BD51
2.Register the Function module in WE57 .
3.we42 Process code .
4. WE20 -PARTNER Profile
I hope it resolves ur Query.
Rgds
Sree M

IDOC inbound function module!

Has anybody worked on IDOC inbound function module !
What is the meaning of the following steps !
IDOC_STATUS-DOCNUM = IDOC_CONTROL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-MSGTY = 'E'
IDOC_STATUS-MSGID = ' ZE'
IDOC_STATUS-MSGNO = '007'
IDOC_STATUS-MSGV1 = IT_LIKP-vbeln.
APPEND IDOC_STATUS.
What are possible values for MSGTY,MSGID, MSGNO.....
What do they mean !
Edited by: Alvaro Tejada Galindo on Mar 10, 2008 7:18 PM

"here nothing complicated ...
"status 51 means 'Application document not posted'
"in WE02 you can see this message
IDoc: 0000000000001254 Status: Application document not posted
IDOC_STATUS-DOCNUM = IDOC_CONTROL-DOCNUM. "IDoc number
IDOC_STATUS-STATUS = '51'.                                      "stauts code
IDOC_STATUS-MSGTY = 'E'                                         "error type
IDOC_STATUS-MSGID = ' ZE'                                       "message class ID
IDOC_STATUS-MSGNO = '007'                                     "message number in ZE
IDOC_STATUS-MSGV1 = IT_LIKP-vbeln.                      "document number or order number
APPEND IDOC_STATUS.

SD: IDOC: Missing functions

Similar Messages

Maybe you are looking for