IDOC FM Error: GETWA_NOT_ASSIGNED

Hello everyone,
FILE > XI > IDOC
I have a scenario where I copy a function module (IDOC_INPUT_ORDERS to ZIDOC_INPUT_ORDERS) and make changes to the code to enhance the program. I get an error 'GETWA_NOT_ASSIGNED' 'Field symbol has not yet been assigned' on the shortdump.
This is strange since even if I don't make any major changes (eg. write a *note in the zprogram), whenever I run it, it gives me the above error. Has anyone encountered this before? If so, would anyone be able to help me out?
Thanks in advance!
Glenn

Hi Glenn
The solution is in this thread
/thread/702726 [original link is broken]
The problem is most likely due to an inconsistency in the infoobject,
perhaps during activation.
In order to solve this problem, you should do the following:
1) Go to transaction RSD1
2) make a "dummy" change to the infoobject 0G_CWWREP, for example, by
adding a "." to the long description of the infoobject
3) save this change and activate the infoobject.
4) now change the text back to original text
5) save this change and activate the infoobject again
6) now reactivate the transfer rules for this
7) now try the load again
Regards
Abhishek
**Please reward points if helpful**

Similar Messages

Idoc posting dump error GETWA_NOT_ASSIGNED

Hello,
While trying to post an inbound shipping notification
Process code DELS msgtyp DESADV idoc type delvry01
iam getting a dump error GETWA_NOT_ASSIGNED Iam using standard fun module..Can anyone help why that dump happens...?
while the fun module hits the first perform DESADV_IDOC_PARSE the dump happens in the statement shown..
The error is Field symbol has not yet been assigned but its a std module iam using...
Can you pls help..
Thanks,
Larry
000470   * check basis idoc type
     >     READ TABLE IDOC_CONTRL INDEX 1.
000490     IF IDOC_CONTRL-IDOCTP NE 'DELVRY01'.
000500       MESSAGE E029(E0) WITH IDOC_CONTRL-IDOCTP TEXT-001
000510               'IDOC_INPUT_DELVRY1' RAISING WRONG_FUNCTION_CALLED.
000520     ENDIF.
000530
000540     CLEAR:   F_STAT, F_TIDX, T_DLGN, T_VSEK, T_VSEP,
000550              S_DL20, S_DT13, S_DRM1, S_DRE1, S_DL24,
000560              S_DL41, S_DL37, S_DL44.
000570     REFRESH: T_DLGN, T_VSEK, T_VSEP.

Iam using 4.0 version of SAP
Larry

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Runtime Error -GETWA_NOT_ASSIGNED when running COI

Hi ALL,
We are getting run time error - GETWA_NOT_ASSIGNED when running COI tasks.
Error analysis
 You attempted to access an unassigned field symbol
 (data segment 32995).
 This error may occur for any of the following reasons:
 - You address a typed field symbol before it is set using ASSIGN
 - You address a field symbol that points to a line in an internal table
 that has been deleted
 - You address a field symbol that had previously been reset using
 UNASSIGN, or that pointed to a local field that no longer exists
 - You address a global function interface parameter, even
 though the relevant function module is not active,
 that is it is not in the list of active calls. You can get the list
 of active calls from the this short dump.
How to correct the error
 You may able to find an interim solution to the problem
 in the SAP note system. If you have access to the note system yourself,
 use the following search criteria:
 "GETWA_NOT_ASSIGNED" C
 "CL_UC_COI_ACT_PT==============CP" or "CL_UC_COI_ACT_PT==============CM00P"
 "REDUCE_GOODWILL_ENTRIES"
 If you cannot solve the problem yourself and you wish to send
 an error message to SAP, include the following documents:
 1. A printout of the problem description (short dump)
 To obtain this, select in the current display "System->List->
 Save->Local File (unconverted)".
2. A suitable printout of the system log
 To obtain this, call the system log through transaction SM21.
 Limit the time interval to 10 minutes before and 5 minutes
 after the short dump. In the display, then select the function
 "System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, select the Editor function "Further Utilities->
 Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
Information on where terminated
 The termination occurred in the ABAP program "CL_UC_COI_ACT_PT==============CP"
 in "REDUCE_GOODWILL_ENTRIES".
 The main program was "UCUWB000 ".
 The termination occurred in line 722 of the source code of the (Include)
 program "CL_UC_COI_ACT_PT==============CM00P"
 of the source code of program "CL_UC_COI_ACT_PT==============CM00P" (when
 calling the editor 7220).
702 call method do_inv_net_change->create_data_reference
703 exporting
704 i_type = cl_uc_coi_inv_net=>gc_ref_pt_block
705 io_model = do_model
706 importing
707 er_data = lr_t_data.
708 assign lr_t_data->* to <lt_share_block>.
709 call method do_inv_net_change->get_block
710 importing
711 et_pt_shares = <lt_share_block>.
712
713 create data lr_s_data like line of <lt_share_block>.
714 assign lr_s_data->* to <ls_share_block>.
715 * change due to selling invor's transaction
716 read table <lt_share_block> into <ls_share_block> index 1.
717
718 * direct shares prior to divestiture
719 assign component 'R_TH_DSH_OLD'
720 of structure <ls_share_block> to <lr_th_dsh_old>.
721 assign <lr_th_dsh_old>->* to <lt_dsh_old>.
>>>> create data lr_s_data like line of <lt_dsh_old>.
723 assign lr_s_data->* to <ls_dsh_old>.
724 assign component ucf6_cs_coi_fld-pcnt1
725 of structure <ls_dsh_old> to <pcnt1_7a>.
726
727 * change of direct shares in divestiture
Please provide your suggestions.
Edited by: VM2727 on Feb 10, 2012 3:27 AM

Or even these ones:
SAP Note 1480856 - C/I: Program termination GETWA_NOT_ASSIGNED
Symptom
When you execute the consolidation of investments, a program termination
occurs (short dump GETWA_NOT_ASSIGNED in the method CREATE_OCI_LIST of the
class CL_UC_COI_ACT).
Note 1467924 - Termination GETWA_NOT_ASSIGNED in CL_UC_COI_ACT_PD
Symptom
When you execute the consolidation of investments, the program termination GETWA_NOT_ASSIGNED occurs in the method CALC_NET_INCOME_MEM of the class CL_UC_COI_ACT_PD.

IDOC Syntax Error E0072 with status 26 after upgrade to ECC6.0

Hi
We have upgraded SAP R/3 from 4.6C to ECC6.0. After upgrade, when we create PO and output EDI, we are seeing this IDOC syntax error E0072 for Mandatory Segment E1EDK01. In 4.6C it was working fine with no issues, only after upgrade this problem started. It says E1EDK01 is missing which is mandatory. We are using basic type ORDERS01 with no extensions. When we see WE30 it looks fine, WE20 settings looks fine.
Order of the segments got scrambled in upgraded version. First segment is E1EDP19001, this is supposed to be under E1EDP01 segment. There are two E1EDP19001 segments created but there were no sub segments to E1EDP01.
Any help in this regard is highly appreciated.
Thanks
Pandiri

User Exit activation and fixing the issue in user exit fixed this issue.

T-code MDBT runtime error GETWA_NOT_ASSIGNED

Hell everyone.
I copied a client from another client,then I runned MRP in the new client by T-code MDBT.
It happened an error.
Can anybody tell me how I can reslove this issue?
Thanks & Best regards!
The detail error as below:
Runtime Errors         GETWA_NOT_ASSIGNED
Date and Time          2010.06.19 11:01:46
Kurztext
     Field symbol has not yet been assigned.
发生了什么?
     Error in ABAP application program.
     The current ABAP program "FCR05205" had to be terminated because one of the
     statements could not be executed.
     This is probably due to an error in the ABAP program.
你能做什么?
     Print out the error message (using the "Print" function)
     and make a note of the actions and input that caused the
     error.
     To resolve the problem, contact your SAP system administrator.
     You can use transaction ST22 (ABAP Dump Analysis) to view and administer
      termination messages, especially those beyond their normal deletion
     date.
     is especially useful if you want to keep a particular message.
错误分析
    You attempted to access an unassigned field symbol
    (data segment 11).
    This error may occur for any of the following reasons:
    - You address a typed field symbol before it is set using ASSIGN
    - You address a field symbol that points to a line in an internal table
      that has been deleted
    - You address a field symbol that had previously been reset using
      UNASSIGN, or that pointed to a local field that no longer exists
    - You address a global function interface parameter, even
      though the relevant function module is not active,
      that is it is not in the list of active calls. You can get the list
      of active calls from the this short dump.
如何更正此错误
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system your
    use the following search criteria:
    "GETWA_NOT_ASSIGNED" C
    "FCR05205" or "FCR05F00"
    "PUT_P_VGWXX"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".
    2. A suitable printout of the system log
       To obtain this, call the system log through transaction SM21.
       Limit the time interval to 10 minutes before and 5 minutes
       after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, select the Editor function "Further Utilities->
       Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
     or which actions and input led to the error.
Edited by: lzjsdxg on Jun 19, 2010 6:35 AM

Are there anybody can help me?
Thanks!

Status 56 - IDOC with errors added

Hi everyone,
 I was configuring File to IDOC Scenario, in the receiving R/3 system, i am getting error as Status 56 - IDOC with errors added "EDI: Partner Profile not available".
 but i had already created Partner profile in WE20.
Regards,
Varun Reddy.K

Hi Varun,
 The below link will help u in solving u r problem
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Just try follow the steps followed in above mentioned link
And also check u r RFC connection in TC "SM59".
Reward with ponits if helpful
Regards
Sai Ganesh

Package failed with run time error: " GETWA_NOT_ASSIGNED".

Hi,
One of our custom package is failing with run time error " GETWA_NOT_ASSIGNED". We are getting this error after refresh. Infact this package is working fine both in production and Dev, but in QA system it giving runtime error.
Here with I am pasting run time error details. Please see...If any one have any idea or clue or if you have faced this kind of error.
Thanks is advance.
Error Details.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_UJK_CUSTOM_LOGIC===========CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    You attempted to access an unassigned field symbol
    (data segment 32774).
    This error may occur if
    - You address a typed field symbol before it has been set with
      ASSIGN
    - You address a field symbol that pointed to the line of an
      internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
Regards, Trine

Hi Trine,
the error is about some field you are trying to map using field-simbols, that is diferent in the other system.
Go to the code program in the st22, there you will see when the erros occurs e what field gives the error.
Best Regards,
António

Error in Receiver - IDoc with errors added

Hi All,
I am getting error in 56 - IDoc with errors added in receiver System.
I am new in Idoc - please tell me How to resolve this issue..
Thanks in advance..

Hi all thanks for reply .
All are the help full answer ,
I use T-code WE19 and change partner profile and execute now it is fine.
But i have checked all configuration regard partner profile from T-code WE20 it looking everything is fine but in Test tool for Idoc Processing by t-code WE19 i have checked it will taken wrong partner profile detail after giving correct manually now it is working fine.

IDOC AAE error:IDOC_ERROR_PARSE_FAILURE

Hello Gurus,
I am facing following error in IDOC AAE channel scenario is SOAP to IDOC we are using Integrated configuration.I have mapped all the attributes in the IDOC to 1 and date formats are fine.On Analsys i found for the IDOC Field MENGE is not accepting Decimal values when the value 868.000 is passed IDOC AAE is failing with following error.
When i pass with out decimal like 868 Idoc is posting successfully.
using connection
File_http://sap.com/xi/XI/System failed, due to:
com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to
idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException
occurred while parsing IDocXML for type :state=READING_FIELD_VALUE_TAG,
charPosition=441, lineNumber=1, columnNumber=442" tabIndex=0
ti="0" lsdata="{0:'Transmitting the message to endpoint using
connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException:
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE:
An IDocConversionException occurred while parsing IDocXML for type
:\nstate=READING_FIELD_VALUE_TAG, charPosition=441, lineNumber=1,
columnNumber=442',7:true}" ct="TV"
bMarkedAsFocussed="true" bResetTabIndex="true"Transmitting
the message to endpoint <local> using connection
File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException:
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE:
An IDocConversionException occurred while parsing IDocXML for type
<Z2MAK075IDOC>:
state=READING_FIELD_VALUE_TAG, charPosition=441, lineNumber=1, columnNumber=442
I have explored through forum but i didnt find exact solution how decimal values can be handled in IDOC AAE .Please through some light on the issue any help is higly apprecaited.
Regards
Praveen Maareddy

Hi Praveen
Looks like it will not allow dot(.) or comma(,) .
Check this
A numc field will not allow you to post values like '.' or ',' to it. You need to get rid of the decimal point/comma. You can do that by multiplying the value by 100 or 1000... depending on your decimal places. Then it is possible to post that values to a numc field. A numc does allow only the numeric characters from 0 to 9. If this is not what you want (because you are dealing with an characteristic) you need to use a char infoobject or you need to use a keyfigure.
Problem with conversion char to numc in transference rules
You can change the data type of MENGE like below
result TYPE p LENGTH 8 DECIMALS 3.

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML

Hello Rescue Team,
I am facing the following error :\
16.06.2014 23:22:42.164
Error
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.166
Error
MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
and the payload transferred is as attached in the attachment below.
I have refered various blogs, however I am still not able to understand how to get the exact location of the error location..According to me, the value that is giving trouble is OTH in <BSARK> however I have checked the permitted values for BSARK on ECC and OTH is maintained.
Can you please help how I can resolve this error.
Thanks
Saurabh

Hi Guys,
This is solved..I corrected the date format of the ZZTIME segment from 1157 to 115700.
Thanks
Saurabh

Run time Errors GETWA_NOT_ASSIGNED at Time of Print Reports.

Hello hy All experts.
I ma trying to print Reports, but at time of preview i got an error message. Run time Errors GETWA_NOT_ASSIGNED.
Please Give me Solutions.
Thnks
Bhavesh Panchal.
Baroda

FORM fetch_data.
break mtabap.
SELECT *
          FROM vbep
          INTO TABLE it_vbep
          WHERE edatu IN so_edatu
          AND vbeln IN so_vbeln.
IF NOT it_vbep[] IS INITIAL.
    SELECT *
                   FROM vbak
                   INTO TABLE it_vbak
                   FOR ALL ENTRIES IN it_vbep
                   WHERE vbeln = it_vbep-vbeln
                   AND kunnr IN so_kunnr.
ENDIF.
IF NOT it_vbak[] IS INITIAL.
    SELECT *
            FROM vbpa
            INTO TABLE it_vbpa
            FOR ALL ENTRIES IN it_vbak
            WHERE vbeln = it_vbak-vbeln
            AND   posnr = space.
    SELECT *
             FROM vbap
             INTO TABLE it_vbap
             FOR ALL ENTRIES IN it_vbak
             WHERE vbeln = it_vbak-vbeln.
Select all Customer Data
    SELECT * FROM kna1 INTO TABLE it_kna1
    FOR ALL ENTRIES IN it_vbak
    WHERE kunnr = it_vbak-kunnr .
    SELECT *
             FROM vbkd
             INTO TABLE it_vbkd
             FOR ALL ENTRIES IN it_vbap
             WHERE vbeln = it_vbap-vbeln.
           and posnr = IT_VBAP-POSNR.
    SELECT *
             FROM vbbe
             INTO TABLE it_vbbe
             FOR ALL ENTRIES IN it_vbap
             WHERE vbeln = it_vbap-vbeln
             AND posnr = it_vbap-posnr.
    SELECT *
             FROM vbup
             INTO TABLE it_vbup
             FOR ALL ENTRIES IN it_vbap
             WHERE vbeln = it_vbap-vbeln
             AND posnr = it_vbap-posnr.
    SELECT *
             FROM konv
             INTO TABLE it_konv
             FOR ALL ENTRIES IN it_vbak
             WHERE knumv = it_vbak-knumv
             AND kinak = space .
    SELECT *
          FROM vbrp
          INTO TABLE it_vbrp
          FOR ALL ENTRIES IN it_vbak
          WHERE aubel = it_vbak-vbeln.
    IF NOT it_vbrp[] IS INITIAL.
      SELECT * FROM likp
                        INTO TABLE it_likp
                        FOR ALL ENTRIES IN it_vbrp
                        WHERE vbeln = it_vbrp-vgbel.
      SELECT * FROM lips
                        INTO TABLE it_lips
                        FOR ALL ENTRIES IN it_vbrp
                        WHERE vbeln = it_vbrp-vgbel
                        AND posnr = it_vbrp-vgpos.
    ENDIF.
ENDIF.
LOOP AT it_vbap.
    itab-posnr = it_vbap-posnr.
    itab-posar = it_vbap-posar.
ITAB-BRGEW = IT_VBAP-BRGEW.
    itab-brgew = it_vbap-brgew.
    itab-ntgew = it_vbap-ntgew.
    READ TABLE it_vbak WITH KEY vbeln = it_vbap-vbeln.
    itab-vbeln = it_vbak-vbeln.
    itab-netwr = it_vbak-netwr.
    itab-kunnr = it_vbak-kunnr.
    READ TABLE it_vbep WITH KEY vbeln = it_vbap-vbeln.
    itab-edatu = it_vbep-edatu.
    READ TABLE it_kna1 WITH KEY kunnr = it_vbak-kunnr.
    itab-name1 = it_kna1-name1.
    READ TABLE it_vbkd WITH KEY vbeln = it_vbap-vbeln .
    itab-bstdk = it_vbkd-bstdk.
    itab-bstkd = it_vbkd-bstkd.
    READ TABLE it_vbrp WITH KEY aubel = it_vbap-vbeln aupos = it_vbap-posnr.
    READ TABLE it_lips WITH KEY vbeln = it_vbrp-aubel posnr = it_vbrp-aupos.
    itab-delivery = it_lips-vbeln.
    itab-lfimg = it_lips-lfimg.
    READ TABLE it_likp WITH KEY vbeln = it_vbrp-aubel   .
    itab-lfdat = it_likp-lfdat.
   itab-ntgew = it_likp-ntgew.
    break mtabap.
    READ TABLE it_vbup WITH KEY vbeln = it_vbap-vbeln posnr = it_vbap-posnr.
    itab-lfsta = it_vbup-lfsta.
    READ TABLE it_vbep WITH KEY vbeln = it_vbap-vbeln posnr = it_vbap-posnr.
    itab-wmeng = it_vbep-wmeng .
    itab-bmeng = it_vbep-bmeng.
    READ TABLE it_vbbe WITH KEY vbeln = it_vbap-vbeln posnr = it_vbap-posnr.
    itab-omeng = it_vbbe-omeng .
    READ TABLE it_konv WITH KEY knumv = it_vbak-knumv
                                kposn = it_vbap-posnr
                                kschl = 'PR00'.
   ITAB-KBETR = IT_KONV-KBETR / 10. " CONDITION RATE
    itab-kbetr = it_konv-kbetr.
    itab-kwert = it_konv-kwert . "CONDITION VALUE
   itab-pending_val = ITAB-OMENG * ITAB-KWERT .
    itab-pending_val = itab-omeng * itab-kbetr .
    APPEND itab.
ENDLOOP.
ENDFORM. "data_retrieval
*&      Form build_listheader
      text
     -->IT_LISTHEADER text
Show quoted text -
FORM build_listheader USING it_listheader TYPE slis_t_listheader.
DATA HLINE TYPE SLIS_LISTHEADER.
DATA: ls_line TYPE slis_listheader.
bhavesh
HLINE-INFO = 'report Developed by Bhavesh'.
HLINE-TYP = 'H'.
Header
Bhavesh
CLEAR ls_line.
ls_line-typ = 'H'.
LS_LINE-KEY: not used for this type
ls_line-info = 'Sales ORDER Report'.
APPEND ls_line TO it_listheader.
bhavesh
***Selection
CLEAR ls_line.
ls_line-typ = 'S'.
ls_line-key = 'Key 1'.
ls_line-info = 'SFEL'.
APPEND ls_line TO it_listheader.
ls_line-key = 'Key 2'.
ls_line-info = 'SFEL'.
APPEND ls_line TO it_listheader.
***Action
CLEAR ls_line.
ls_line-typ = 'A'.
LS_LINE-KEY: not used for this type
ls_line-info = 'Status list'.
APPEND ls_line TO it_listheader.
ENDFORM. "BUILD_LISTHEADER
*ENDFORM. "build_listheader
*&      Form display
*&       text
FORM display.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          i_callback_program      = sy-repid
         i_callback_top_of_page = 'TOP_OF_PAGE'
          is_layout               = alv_layout
          it_fieldcat             = i_fieldcat
         it_events               = gt_events[]
          i_callback_user_command     = 'USER_COMMAND'
          i_grid_title            = 'BHAVESH REPORT'
        TABLES
          t_outtab                = itab[].
CLEAR : itab .
ENDFORM.                    "display
*&      Form top_of_page
      text
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary = it_listheader[].
i_logo = 'ENJOYSAP_LOGO'.
I_END_OF_LIST_GRID =
ENDFORM. "TOP_OF_PAGE

Idoc INVOIC - error Tax entry not possible in this item - Message no. FF724

Hello,
I have an idoc in error with the following error message.
In the idoc type INVOIC
Segment E1EDK04:
MWSKZ     N1     VAT indicator
MSATZ     19.000     VAT rate
MWSBT     20.52     Value added tax amount
In OBCD
Partn.Type PartnerNo Tax type Tax rate Cty Tx
LI         FNISL     N1       19.000       V2
Input tax N6 is defined in the system with rate 19.000%
Direction         2     Inbox
Current status    51
Basic type        INVOIC01
Extension
Message type      INVOIC
Partner No.       FNISL
Partn.Type        LI
Tax entry not possible in this item
Message no. FF724
Diagnosis
You can not enter a tax amount in this item since, due to the posting amount entered and the tax code, a total tax amount of zero has been calculated.
This could either be due to the fact that the tax code has been defined with a value of 0%, or because the posting amount entered (that is, the tax base) is too small.
Example:
With a tax rate of 15%, a tax amount greater than zero will only be achieved with a base amount greater than 0.04. With values of 0.03 and less, it is therefore not possible to enter a tax amount.
Procedure
Only enter tax amounts in conjunction with tax codes for which a percentage rate not equal to zero has been defined. Make sure that in documents with several G/L account items you enter the total tax amount in an item with a sufficiently high posting amount.
do you have an idea to solve it?
Regards
Arnaud

Message no. FF724
Check note 681538
thanks
G. Lakshmipathi

HRMD_A IDoc in error not raising an event

I have workflows enabled for IDocs in error.
If an inbound order IDoc (ORDERS) arrives in status 51, it triggers a workflow.
If an HR master data IDoc (message type HRMD_A) arrives in status 51, no workflow is triggered.
Here is what I have checked:
Partner profile has me as responsible agent in both cases.
Both type linkages are active for IDOCHRMD and IDOCORDERS event InputErrorOccurred.
Both IDocs types are posted in with the test tool and end up in status 51.
When I investigate the event trace, I can see that an event is raised for the ORDERS IDoc but not for the HRMD_A IDoc.
There are no errors in the type linkage status column.
So why would it be that the event is not being raised for the HRMD_A IDoc?
How can I find out what should be raising the event? I guess that there is a function module call to SWE_EVENT_CREATE or SAP_WAPI_CREATE_EVENT.
Kind Regards,
Tony.

Hi Tony,
I am a complete novice to workflow but I have a requirement liek yours to trigger workflow for idocs in error, so I was hoping you could point me in the direction of some documentation/steps on how to do this?

RBDMANI2 for IDOCs in error not working in Background..

Dear All,
 We have an ALE-IDOC scenario in which our IDOC gets posted in the destination system with status 51 as per business reqt. We schedule a job in the background using program RBDMANI2 which is used to manually reprocess IDOCS in error.
 This background job was working fine in the 4,7 R/3 Server, but we have upgarded the receiving system to ECC 6.0. Now the problem is dat when we try to reprocess the IDOC using this job, the IDOC are not processing further.. It ideally is supposed to do further processing as per the code writen.
We tried debugging the code(RBDMANI2) in background. But, its not helping.
Kindly advise.
Regards,
Santosh Reddy.

On primary research I found that there is a call to this FM 'SAPGUI_PROGRESS_INDICATOR' .
In that FM see line 12.
IF SY-BATCH <> SPACE.
 EXIT. "do nothing in batch
 ENDIF.
May be this is the cause of your error.
Rhea.

IDOC FM Error: GETWA_NOT_ASSIGNED

Similar Messages

Maybe you are looking for