EDI 940 and 945 Flow

Hi,
In need to know the flow for EDI940 and EDI945.Can some one help on this.
Many thanks

Hello Anikesh
You may have a look at [Note 104606 - EDI/IDoc: Mapping IDoc types to ANSI X12|https://service.sap.com/sap/support/notes/104606]
At Lindt we are using SHPORD.DELVRY03 in the UK and DESADV.DELVRY03 in Switzerland for shipping orders (940).
In case of shipping confirmations (945) we use both SHPCON.DELVRY03 and WHSCON.DELVRY03.
Regards
Uwe

Similar Messages

Event 940 and 945 Check

Hi
I need to put a check at event 940 and or 945. I need to check the Business area wise total should be Zero. If BA sum not Zero than exclude from transfer. This check is at reconciliation key level.
Events 945: This event calling record by record and pass on.
Regards
Srini

Hello. I'm not sure these 2 events will help you achieve the requirement. Event 940 is used to change the text and "assignment" filed of transferred document. Not sure you can actually stop the transfer in there. Same in event 945 where you can change CO account assignments.
Have you considered implementing the logic on the creation of the FI-CA document? Explore event 0040 for example.
I don't see why you're creating a document that does not need to be transferred to GL.
Jean-Marie

Idoc type, message type and process code for EDI 940 & 945

Hi,
We are implementing a scenario wherein we are required to send a Wharehouse Shipping Order to the warehouse (forwarding agent) using EDI 940. The output of the o/b is triggered from the Delivery (VA01) after creation of a Delivery in SAP. Once the warehouse ships the goods, it notifies us back by sending EDI 945 (Warehouse Shipping Advice). Using this inbound 945 we are required to update the existing delivery in SAP, i.e., it should do the Pick, Pack and PGI.
Can someone tell me which Idoc type, Message Type and Process code should be used for the above scenario.
Thanks in advance for the help.
Regards,
Gajendra

Hi Gajendra,
For EDI940, you can use message type SHPORD or WHSORD, IDOC type DELVRY01 and process code DELV.
For EDI945, you can use message type SHPCON or WHSCON, IDoc type DELVRY01 and process code DELV.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

MB51 - Movement types 531 and 945

Hi To All,
in MB51 i have two movement types 531 and 945. my customer want that this two movements behave like the 101 so with the stock category Q for Quality.
i tried OMJJ but i cannot find where to indicate the quality stock.
can you please suggest?
thanks C.

Hi,
Yes thats right for receiving inspection you need to use inspection type 01 in the quality view inspection set up tab in the material
master which will then flow to delivery tab in the PO as Quality stock and when you do MIGO it will deafult from PO
But to clear it from Quality inspection you will have to maintain Qaulity master data like ispection plan and Q info record
Thanks
Diwakar

Problem with context mapping and data flow in a FPM application

Hi All,
I am trying to develop an ESS application using FPM. For the same, the requirement is to see the history of an employee in the second view.
The first view has got just the overview information and the second one has got the detail. So, the records or the fields are the same on both the views.
As per the FPM guidelines, the Model is residing in the Fc component and the respective Vc components are using the model data accordingly.
I am executing the model in the Fc component calling the executable method in the interfaceController of the first view and then trying to display the output data of the BAPI in the first view which provides the overview information.This is working fine.
But when i am trying to map the same output node to the Table UI for the second view, the record size is coming zero and thus no information is available.
For the above issue, I am again executing the RFC in the InterfaceController of the second view to populate the records, which is incorrect as it is already executed and the data is available for the first view.
I request you to let me know the correct approach to Context mapping and data flow when using FPM-roadmap. Is their any standard method or approach available to deal with such requirements? Please let me know.
Thanks in advance.
Regards
DK

Hi Idhaya,
I model node is available in Fc and the Fc interface controller is being used in the first Vc and the second Vc.
So the idea is, as the executable method is generated in the Fc, so i have created a custom method to call the executable method in Fc, where the input parameter is getting passed and this custom method is finally getting called is the first Vc.
So , now my first Vc is ready to call the custom method in Fc and execute the RFC. Once the RFC is executed, the nodes in the Fc should get populated which is the ideal case.
And as the Fc is used as a component in the second Vc, the same node is available to the UI elements.
But, when I check the record size for the output node, it is always zero, for the second Vc.
Regards
DK

How can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.

how can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.?
please explain the important questions.

How to deal with table control / step loop in BDC
Steploop and table contol is inevitable in certain transactions. When we run BDC for such transactions, we will face the situation: how many visible lines of steploop/tablecontrol are on the screen? Although we can always find certain method to deal with it, such as function code 'NP', 'POPO', considering some extreme situation: there is only one line visible one the screen, our BDC program should display an error message. (See transaction 'ME21', we you resize your screen to let only one row visible, you can not enter mutiple lines on this screen even you use 'NP')
Now with the help of Poonam on sapfans.com developement forum, I find a method with which we can determine the number of visible lines on Transaction Screen from our Calling BDC program. Maybe it is useless to you, but I think it will give your some idea.
Demo ABAP code has two purposes:
1. how to determine number of visible lines and how to calculte page number;
(the 'calpage' routine has been modify to meet general purpose usage)
2. using field symbol in BDC program, please pay special attention to the difference in Static ASSIGN and Dynamic ASSIGN.
Now I begin to describe the step to implement my method:
(I use transaction 'ME21', screen 121 for sample,
the method using is Call Transation Using..)
Step1: go to screen painter to display the screen 121, then we can count the fixed line on this screen, there is 7 lines above the steploop and 2 lines below the steploop, so there are total 9 fixed lines on this screen. This means except these 9 lines, all the other line is for step loop. Then have a look at steploop itselp, one entry of it will occupy two lines.
(Be careful, for table control, the head and the bottom scroll bar will possess another two fixed lines, and there is a maximum number for table line)
Now we have : FixedLine = 9
              LoopLine = 2(for table control, LoopLine is always equal to 1)
Step2: go to transaction itself(ME21) to see how it roll page, in ME21, the first line of new page is always occupied by the last line of last page, so it begin with index '02', but in some other case, fisrt line is empty and ready for input.
Now we have: FirstLine = 0
          or FirstLine = 1 ( in our case, FirstLine is 1 because the first line of new page is fulfilled)
Step3: write a subroutine calcalculating number of pages
(here, the name of actual parameter is the same as formal parameter)
global data:    FixedLine type i, " number of fixed line on a certain screen
                LoopLine type i, " the number of lines occupied by one steploop item
                FirstLine type i, " possbile value 0 or 1, 0 stand for the first line of new                                                               " scrolling screen is empty, otherwise is 1
                Dataline type i, " number of items you will use in BDC, using DESCRIBE to get
                pageno    type i, " you need to scroll screen how many times.
                line      type i, " number of lines appears on the screen.
                index(2) type N, " the screen index for certain item
                begin     type i, " from parameter of loop
                end       type i. " to parameter of loop
*in code sample, the DataTable-linindex stands for the table index number of this line
form calpage using FixedLine type i (see step 1)
                   LoopLine type i (see step 1)
                   FirstLine type i (see step 2)
                   DataLine type i ( this is the item number you will enter in transaction)
          changing pageno    type i (return the number of page, depends on run-time visible                                                                             line in table control/ Step Loop)
          changing line      type i.(visible lines one the screen)
data: midd type i,
      vline type i, "visible lines
if DataLine eq 0.
   Message eXXX.
endif.
vline = ( sy-srows - FixedLine ) div LoopLine.
*for table control, you should compare vline with maximum line of
*table control, then take the small one that is min(vline, maximum)
*here only illustrate step loop
if FirstLine eq 0.
        pageno = DataLine div vline.
        if pageno eq 0.
           pageno = pageno + 1.
        endif.
elseif FirstLine eq 1.
        pageno = ( DataLine - 1 ) div ( vline - 1 ) + 1.
        midd = ( DataLine - 1 ) mod ( vline - 1).
        if midd = 0 and DataLine gt 1.
                pageno = pageno - 1.
        endif.
endif.
line = vline.
endform.
Step4 write a subroutine to calculate the line index for each item.
form calindex using Line type i (visible lines on the screen)
                    FirstLine type i(see step 2)
                    LineIndex type i(item index)
          changing Index type n.    (index on the screen)
if FirstLine = 0.
        index = LineIndex mod Line.
        if index = '00'.
                index = Line.
        endif.
elseif FirstLine = 1.
        index = LineIndex mod ( Line - 1 ).
        if ( index between 1 and 0 ) and LineIndex gt 1.
                index = index + Line - 1.
        endif.
        if Line = 2.
                index = index + Line - 1.
        endif.
endif.
endform.
Step5 write a subroutine to calculate the loop range.
form calrange using Line type i ( visible lines on the screen)
                    DataLine type i
                    FirstLine type i
                    loopindex like sy-index
        changing    begin type i
                    end type i.
If FirstLine = 0.
   if loopindex = 1.
        begin = 1.
        if DataLine <= Line.
                end = DataLine.
        else.
                end = Line.
        endif.
   elseif loopindex gt 1.
        begin = Line * ( loopindex - 1 ) + 1.
        end   = Line * loopindex.
        if end gt DataLine.
           end = DataLine.
        endif.
   endif.
elseif FirstLine = 1.
if loopindex = 1.
        begin = 1.
        if DataLine <= Line.
                end = DataLine.
        else.
                end = Line.
        endif.
elseif loop index gt 1.
        begin = ( Line - 1 ) * ( loopindex - 1 ) + 2.
        end =   ( Line - 1 ) * ( loopindex - 1 ) + Line.
        if end gt DataLine.
                end = DataLine.
        endif.
endif.
endif.
endform.
Step6 using field sysbol in your BDC, for example: in ME21, but you should calculate each item will correponding to which index in steploop/Table Control
form creat_bdc.
field-symbols: <material>, <quan>, <indicator>.
data: name1(14) value 'EKPO-EMATN(XX)',
      name2(14) value 'EKPO-MENGE(XX)',
      name3(15) value 'RM06E-SELKZ(XX)'.
assign:         name1 to <material>,
                name2 to <quan>,
                name3 to <indicator>.
do pageno times.
if sy-index gt 1
*insert scroll page ok_code"
endif.
        perform calrange using Line DataLine FirstLine sy-index
                         changing begin end.
loop at DataTable from begin to end.
        perform calindex using Line FirstLine DataTable-LineIndex changing Index.
        name1+11(2) = Index.
        name2+11(2) = Index.
        name3+12(2) = Index.
        perform bdcfield using <material> DataTable-matnr.
        perform bdcfield using <quan>     DataTable-menge.
        perform bdcfield using <indicator> DataTable-indicator.
endloop.
enddo.
An example abap program of handling Table Control during bdc programming.
REPORT zmm_bdcp_purchaseorderkb02
       NO STANDARD PAGE HEADING LINE-SIZE 255.
                Declaring internal tables                            *
*-----Declaring line structure
DATA : BEGIN OF it_dummy OCCURS 0,
         dummy(255) TYPE c,
       END OF it_dummy.
*-----Internal table for line items
DATA : BEGIN OF it_idata OCCURS 0,
          ematn(18),      "Material Number.
          menge(13),      "Qyantity.
          netpr(11),      "Net Price.
          werks(4),       "Plant.
          ebelp(5),       "Item Number.
        END OF it_idata.
*-----Deep structure for header data and line items
DATA : BEGIN OF it_me21 OCCURS 0,
           lifnr(10),      "Vendor A/c No.
           bsart(4),       "A/c Type.
           bedat(8),       "Date of creation of PO.
           ekorg(4),       "Purchasing Organisation.
           ekgrp(3),       "Purchasing Group.
           x_data LIKE TABLE OF it_idata,
         END OF it_me21.
DATA : x_idata LIKE LINE OF it_idata.
DATA : v_delimit VALUE ','.
DATA : v_indx(3) TYPE n.
DATA : v_fnam(30) TYPE c.
DATA : v_count TYPE n.
DATA : v_ne TYPE i.
DATA : v_ns TYPE i.
*include bdcrecx1.
INCLUDE zmm_incl_purchaseorderkb01.
                Search help for file                                 *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
    IMPORTING
      file_name     = p_file.
START-OF-SELECTION.
       To upload the data into line structure                        *
CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
      filename = p_file
      filetype = 'DAT'
    TABLES
      data_tab = it_dummy.
    Processing the data from line structure to internal tables       *
REFRESH:it_me21.
CLEAR :it_me21.
LOOP AT it_dummy.
    IF it_dummy-dummy+0(01) = 'H'.
      v_indx = v_indx + 1.
      CLEAR   it_idata.
      REFRESH it_idata.
      CLEAR   it_me21-x_data.
      REFRESH it_me21-x_data.
      SHIFT it_dummy.
      SPLIT it_dummy AT v_delimit INTO it_me21-lifnr
                                       it_me21-bsart
                                       it_me21-bedat
                                       it_me21-ekorg
                                       it_me21-ekgrp.
      APPEND it_me21.
    ELSEIF it_dummy-dummy+0(01) = 'L'.
      SHIFT it_dummy.
      SPLIT it_dummy AT v_delimit INTO it_idata-ematn
                                       it_idata-menge
                                       it_idata-netpr
                                       it_idata-werks
                                       it_idata-ebelp.
      APPEND it_idata TO it_me21-x_data.
      MODIFY it_me21 INDEX v_indx.
    ENDIF.
ENDLOOP.
                To open the group                                    *
PERFORM open_group.
        To populate the bdcdata table for header data                *
LOOP AT it_me21.
    v_count = v_count + 1.
    REFRESH it_bdcdata.
    PERFORM subr_bdc_table USING:   'X' 'SAPMM06E'    '0100',
                                    ' ' 'BDC_CURSOR' 'EKKO-LIFNR',
                                    ' ' 'BDC_OKCODE' '/00',
                                    ' ' 'EKKO-LIFNR' it_me21-lifnr,
                                    ' ' 'RM06E-BSART' it_me21-bsart,
                                    ' ' 'RM06E-BEDAT' it_me21-bedat,
                                    ' ' 'EKKO-EKORG' it_me21-ekorg,
                                    ' ' 'EKKO-EKGRP' it_me21-ekgrp,
                                    ' ' 'RM06E-LPEIN' 'T'.
    PERFORM subr_bdc_table USING:   'X' 'SAPMM06E'    '0120',
                                    ' ' 'BDC_CURSOR' 'RM06E-EBELP',
                                    ' ' 'BDC_OKCODE' '/00'.
    MOVE 1 TO v_indx.
*-----To populate the bdcdata table for line item data
    LOOP AT it_me21-x_data INTO x_idata.
      CONCATENATE 'EKPO-EMATN(' v_indx ')' INTO v_fnam.
      PERFORM subr_bdc_table USING ' ' v_fnam x_idata-ematn.
      CONCATENATE 'EKPO-MENGE(' v_indx ')' INTO v_fnam.
      PERFORM subr_bdc_table USING ' ' v_fnam x_idata-menge.
      CONCATENATE 'EKPO-NETPR(' v_indx ')' INTO v_fnam.
      PERFORM subr_bdc_table USING ' ' v_fnam x_idata-netpr.
      CONCATENATE 'EKPO-WERKS(' v_indx ')' INTO v_fnam.
      PERFORM subr_bdc_table USING ' ' v_fnam x_idata-werks.
      v_indx = v_indx + 1.
      PERFORM subr_bdc_table USING: 'X' 'SAPMM06E'    '0120',
                                     ' ' 'BDC_CURSOR' 'RM06E-EBELP',
                                     ' ' 'BDC_OKCODE' '/00'.
    ENDLOOP.
    PERFORM subr_bdc_table USING:    'X' 'SAPMM06E'    '0120',
                                     ' ' 'BDC_CURSOR' 'RM06E-EBELP',
                                     ' ' 'BDC_OKCODE' '=BU'.
    PERFORM bdc_transaction USING 'ME21'.
ENDLOOP.
PERFORM close_group.
                  End of selection event                             *
END-OF-SELECTION.
IF session NE 'X'.
*-----To display the successful records
    WRITE :/10 text-001.          "Sucess records
    WRITE :/10 SY-ULINE(20).
    SKIP.
    IF it_sucess IS INITIAL.
      WRITE :/ text-002.
    ELSE.
      WRITE :/   text-008,          "Total number of Succesful records
              35 v_ns.
      SKIP.
      WRITE:/   text-003,          "Vendor Number
             17 text-004,          "Record number
             30 text-005.          "Message
    ENDIF.
    LOOP AT it_sucess.
      WRITE:/4 it_sucess-lifnr,
             17 it_sucess-tabix CENTERED,
             30 it_sucess-sucess_rec.
    ENDLOOP.
    SKIP.
*-----To display the erroneous records
    WRITE:/10   text-006.          "Error Records
    WRITE:/10   SY-ULINE(17).
    SKIP.
    IF it_error IS INITIAL.
      WRITE:/   text-007.          "No error records
    ELSE.
      WRITE:/   text-009,          "Total number of erroneous records
             35 v_ne.
      SKIP.
      WRITE:/   text-003,          "Vendor Number
             17 text-004,          "Record number
             30 text-005.          "Message
    ENDIF.
    LOOP AT it_error.
      WRITE:/4 it_error-lifnr,
             17 it_error-tabix CENTERED,
             30 it_error-error_rec.
    ENDLOOP.
    REFRESH it_sucess.
    REFRESH it_error.
ENDIF.
CODE IN INCLUDE.
Include           ZMM_INCL_PURCHASEORDERKB01
DATA:   it_BDCDATA LIKE BDCDATA    OCCURS 0 WITH HEADER LINE.
DATA:   it_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA:   E_GROUP_OPENED.
*-----Internal table to store sucess records
DATA:BEGIN OF it_sucess OCCURS 0,
       msgtyp(1)   TYPE c,
       lifnr LIKE ekko-lifnr,
       tabix LIKE sy-tabix,
       sucess_rec(125),
     END OF it_sucess.
DATA: g_mess(125) type c.
*-----Internal table to store error records
DATA:BEGIN OF it_error OCCURS 0,
       msgtyp(1)   TYPE c,
       lifnr LIKE ekko-lifnr,
       tabix LIKE sy-tabix,
       error_rec(125),
     END OF it_error.
       Selection screen
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS session RADIOBUTTON GROUP ctu. "create session
SELECTION-SCREEN COMMENT 3(20) text-s07 FOR FIELD session.
SELECTION-SCREEN POSITION 45.
PARAMETERS ctu RADIOBUTTON GROUP ctu.     "call transaction
SELECTION-SCREEN COMMENT 48(20) text-s08 FOR FIELD ctu.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s01 FOR FIELD group.
SELECTION-SCREEN POSITION 25.
PARAMETERS group(12).                      "group name of session
SELECTION-SCREEN COMMENT 48(20) text-s05 FOR FIELD ctumode.
SELECTION-SCREEN POSITION 70.
PARAMETERS ctumode LIKE ctu_params-dismode DEFAULT 'N'.
"A: show all dynpros
"E: show dynpro on error only
"N: do not display dynpro
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 48(20) text-s06 FOR FIELD cupdate.
SELECTION-SCREEN POSITION 70.
PARAMETERS cupdate LIKE ctu_params-updmode DEFAULT 'L'.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s03 FOR FIELD keep.
SELECTION-SCREEN POSITION 25.
PARAMETERS: keep AS CHECKBOX.       "' ' = delete session if finished
"'X' = keep   session if finished
SELECTION-SCREEN COMMENT 48(20) text-s09 FOR FIELD e_group.
SELECTION-SCREEN POSITION 70.
PARAMETERS e_group(12).             "group name of error-session
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 51(17) text-s03 FOR FIELD e_keep.
SELECTION-SCREEN POSITION 70.
PARAMETERS: e_keep AS CHECKBOX.     "' ' = delete session if finished
"'X' = keep   session if finished
SELECTION-SCREEN END OF LINE.
PARAMETERS:p_file LIKE rlgrap-filename.
at selection screen                                                *
AT SELECTION-SCREEN.
group and user must be filled for create session
IF SESSION = 'X' AND
     GROUP = SPACE. "OR USER = SPACE.
    MESSAGE E613(MS).
ENDIF.
create batchinput session                                          *
FORM OPEN_GROUP.
IF SESSION = 'X'.
    SKIP.
    WRITE: /(20) 'Create group'(I01), GROUP.
    SKIP.
*----open batchinput group
    CALL FUNCTION 'BDC_OPEN_GROUP'
      EXPORTING
        CLIENT = SY-MANDT
        GROUP = GROUP
        USER   = sy-uname.
    WRITE:/(30) 'BDC_OPEN_GROUP'(I02),
            (12) 'returncode:'(I05),
                 SY-SUBRC.
ENDIF.
ENDFORM.                    "OPEN_GROUP
end batchinput session                                             *
FORM CLOSE_GROUP.
IF SESSION = 'X'.
*------close batchinput group
    CALL FUNCTION 'BDC_CLOSE_GROUP'.
    WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
            (12) 'returncode:'(I05),
                 SY-SUBRC.
ELSE.
    IF E_GROUP_OPENED = 'X'.
      CALL FUNCTION 'BDC_CLOSE_GROUP'.
      WRITE: /.
      WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
    ENDIF.
ENDIF.
ENDFORM.                    "CLOSE_GROUP
       Start new transaction according to parameters                 *
FORM BDC_TRANSACTION USING TCODE TYPE ANY.
DATA: L_SUBRC LIKE SY-SUBRC.
*------batch input session
IF SESSION = 'X'.
    CALL FUNCTION 'BDC_INSERT'
      EXPORTING
        TCODE     = TCODE
      TABLES
        DYNPROTAB = it_BDCDATA.
    WRITE: / 'BDC_INSERT'(I03),
             TCODE,
             'returncode:'(I05),
             SY-SUBRC,
             'RECORD:',
             SY-INDEX.
ELSE.
    REFRESH it_MESSTAB.
    CALL TRANSACTION TCODE USING it_BDCDATA
                     MODE   CTUMODE
                     UPDATE CUPDATE
                     MESSAGES INTO it_MESSTAB.
    L_SUBRC = SY-SUBRC.
    WRITE: / 'CALL_TRANSACTION',
             TCODE,
             'returncode:'(I05),
             L_SUBRC,
             'RECORD:',
             SY-INDEX.
ENDIF.
Message handling for Call Transaction                              *
perform subr_mess_hand using g_mess.
*-----Erzeugen fehlermappe
IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
    IF E_GROUP_OPENED = ' '.
      CALL FUNCTION 'BDC_OPEN_GROUP'
        EXPORTING
          CLIENT = SY-MANDT
          GROUP = E_GROUP
          USER   = sy-uname
          KEEP   = E_KEEP.
      E_GROUP_OPENED = 'X'.
    ENDIF.
    CALL FUNCTION 'BDC_INSERT'
      EXPORTING
        TCODE     = TCODE
      TABLES
        DYNPROTAB = it_BDCDATA.
ENDIF.
REFRESH it_BDCDATA.
ENDFORM.                    "BDC_TRANSACTION
     Form subr_bdc_table                                            *
      text
     -->P_0220   text                                                *
     -->P_0221   text                                                *
     -->P_0222   text                                                *
FORM subr_bdc_table USING      VALUE(P_0220) TYPE ANY
                                VALUE(P_0221) TYPE ANY
                                VALUE(P_0222) TYPE ANY.
CLEAR it_bdcdata.
IF P_0220 = ' '.
    CLEAR it_bdcdata.
    it_bdcdata-fnam     = P_0221.
    it_bdcdata-fval     = P_0222.
    APPEND it_bdcdata.
ELSE.
    it_bdcdata-dynbegin = P_0220.
    it_bdcdata-program = P_0221.
    it_bdcdata-dynpro   = P_0222.
    APPEND it_bdcdata.
ENDIF.
ENDFORM.                    " subr_bdc_table
     Form subr_mess_hand                                            *
      text                                                           *
     -->P_G_MESS text                                               *
FORM subr_mess_hand USING P_G_MESS TYPE ANY.
LOOP AT IT_MESSTAB.
    CALL FUNCTION 'FORMAT_MESSAGE'
      EXPORTING
        ID     = it_messtab-msgid
        LANG   = it_messtab-msgspra
        NO     = it_messtab-msgnr
        v1     = it_messtab-msgv1
        v2     = it_messtab-msgv2
      IMPORTING
        MSG    = P_G_MESS
      EXCEPTIONS
        OTHERS = 0.
    CASE it_messtab-msgtyp.
      when 'E'.
        it_error-error_rec   = P_G_MESS.
        it_error-lifnr       = it_me21-lifnr.
        it_error-tabix       = v_count.
        APPEND IT_ERROR.
      when 'S'.
        it_sucess-sucess_rec = P_G_MESS.
        it_sucess-lifnr      = it_me21-lifnr.
        it_sucess-tabix      = v_count.
        APPEND IT_SUCESS.
    endcase.
ENDLOOP.
Describe table it_sucess lines v_ns.
Describe table it_error lines v_ne.
ENDFORM.                    " subr_mess_hand
Also refer
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/bdc-table-control-668404
and
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
Regards,
srinivas
<b>*reward for useful answers*</b>

Datasource related to FI and Cash Flow

Hi ,can anyone please give me information on FI and Cash Flow management and it's datasource as well.
Regards
Arjun

Hi,
Check the presentation
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
Regards.

Purchase and sales flow resulting from 'production in other plant'.

Dear all,
When using the procurement type 'P' (production in other plant), materials are consumed in plant A and goods receipts from production order happens in plant B.
When plants A and B belong to different company codes, SAP generates a cross-company document. Within the receiving company, the offsetting account for the stock account is the cross-company clearing account.
This posting is generally not sufficient as legal and tax requirements ask for a sales and purchasing flow between the 2 company codes. Therefore many companies need to 'develop a solution' to complete this posting 'after the facts'.
Does anybody know whether this additional posting exists under the form of an 'add-on' or additional solution to the standard made available by one or another partner of SAP ? Note that the starting point for this question is important : our company wants to use the 'production in other plant' flow because the native purchase and sales flows are too much time consuming.
Thanks for your help.
José Beghein

Hi all,
I want to be a bit more accurate here :
The produced material in plant B has a special procurement type code (MARC-SOBSL) which in its definition contains procurement type E (BESKZ) and special procurement P (ESOBS). It is special procurement P that triggers the 'production in other plant' behaviour. The production plant (WRK02) is also specified in the definition of the special procurement type code.
Kind regards.
José Beghein

SSIS Control and Data Flow Items not available in Customize Toolbox

I cannot add additional Data Flow and Control Flow items to the SSIS Toolbox. I am using SQL Server 2014 and VS 2013 (BIDS). The standard SSIS items appear - but they are all of them. How do I add the additional ones that are not loaded by default. I didn't
have this issue with SQL Server 2012.
Thank you,
Johhn
John

John, which ones you do not see? AFAIK nothing has changed regarding how the items get added to SSIS toolbox in SSDT or VS 2013 with SSDT installed (no BIDS in SSIS 2012 and up).
Arthur My Blog

Ways of creating contract and process flow of contracts

hi friends
ways of creating contract and process flow of contracts
thanks for ur help
regards
krishna

hi,
In the MM Purchasing component, a contract is a type of outline purchase agreement against which release orders (releases) can be issued for agreed materials or services as and when required during a certain overall time-frame.
Contracts can take the following forms:
Quantity contracts
Use this type of contract if the total quantity to be ordered during the validity period of the contract is known in advance. The contract is regarded as fulfilled when release orders totaling a given quantity have been issued.
Value contracts
Use this type of contract if the total value of all release orders issued against the contract is not to exceed a certain predefined value. The contract is regarded as fulfilled when release orders totaling a given value have been issued.
You can also set up corporate buying contracts with your vendors. These are valid for all plants and company codes within a client (see Centrally Agreed Contract).
You can create a contract as follows:
Manually
You enter all data relating to the contract manually.
Using the referencing technique
As reference document (the document you copy from), you can use:
Purchase requisitions
RFQs/quotations
Other contracts
CREATION OF CONTRACT MANUALLY:
Choose Outline agreement --> Contract --> Create(ME31K)
The initial screen appears.
Enter the necessary data. If you make any specifications under the group heading Default data, this data will appear as the default data in each item.
In the Agreement type field, specify whether you are creating a quantity or value contract, for example.
Press ENTER .
The header data screen appears.
Enter the contract validity period. Check the other fields on this screen and make any necessary changes (e.g. the terms of payment) and define the header conditions.
Press ENTER .
The item overview screen appears.
On this screen, enter the information for each item (material number, target quantity, price, receiving plant, or account assignment, etc.) using the same procedure as with purchase orders.
Material without a master record: leave the field for the material number empty and enter the following:
u2013 Short description of the relevant material or service in the Short text field
u2013 Material group to which the material belongs, in the Material group field
u2013 Account assignment category
You can enter u (unknown) or the category of an account assignment.
u2013 The target quantity and the order unit
If you specify an account assignment category other than U (field A), you must enter the relevant account assignment data for the item. To do so, choose Item ® Account assignments (see also Account Assignment).
If necessary, review the details for each item. Select the item(s) to review. Then select Item -> Details.
Enter the desired conditions.
Enter further text for the item if any additional instructions to the vendor or Goods Receiving are necessary. Choose Item -> Texts -> Text overview.
Save the contract.
Hope it helps..
Regards
Priyanka.P
AWARD IF HELPFULL
Edited by: Priyanka Paltanwale on Aug 25, 2008 7:20 AM

Seeburger help required for Supplier Invoice (EDI 810) and Dispatch Advice

Hi All,
Pls let me blog/steps for scenario for Supplier Invoice and Dispatch Advice using Seeburger.
For Supplier Invoice I assume R/3 will send data to Vendor (810).
1. Pls let me know for R/3 to XI will we use INVOCE IDOC?
2. Pls let me know for R/3 to XI Communication do we will use same Distributiion Model setup?
3. Pls let me know what Seeburger BIC modules I need to use in Seeburger AS2/File Receiver Adapter
4. Which Interface and Adapter I need to use for 810 and which Interface and Adapter I need to use for 997.
    Pls send its setup with its Mappings defined in Modules.
5. What is Disptach Advice? Is it also same like Supplier Invoice ? Does it also have EDI Number and if yes then what?
Pls send me blogs for the above Supplier Invoice and Dispatch Advice settings.
Regards

>
Rickkk wrote:
> Hi Ravi and All
>
> I am thankful to all of you for great help of yours.
>
> Steps:
>
> 1) I wil create an INvoice in your backend system. It will generate an IDOC.
> 2) This IDOC will be sent to my XI system.
> 3) I will map the IDOC to the Target XML 810 --- From where I will get this Target XML 810 ?
YOu have to login to the Physical box in which XI is installed (Take Basis Help.
In one of the drives, you will find a folder called seeburger.
Inside that folder, you can browse to find the XSD structure for your 810 .
YOu will find different XSDs for different versions of 810.
Suppose your EDI 810 version is 4010, then you have to use the XSD for 810 4010 version (There will be separate folders for each transaction set/version combination.
It will be there also in the software CD that seeburger provides when you buy it.
> 4) I need a seeburger receiver AS2 adapter that consist of modules that will convert the XML 810 docuemnt to EDI document.
>
> Below are the modules will be present in you suggested seeburger receiver AS2 adapter
> module key                  Parameter name               Parameter value
> bic                                destSourceMsg               MainDocument
> bic                                destTargetMsg                MainDocument
> bic                                mappingName                  <the name of your X2E mapping for 810>
> exit                               JNDIName                         deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
>
Yes.
> 5. As per blog -
/people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
>
> For 997 Interface we are using seeburger Sender adapter and for 850 Interface we are using Split997 Sender adapter -- Reverse order
>
> For this scenario will it be like this again like
> For 997 Interface we will use Seeburger Receiver AS2 Adapter where the above modules are configured -- Pls suggest
>
> For 810 Interface we will use Split997 Receiver adapter -- No modules configured Pls suggest
>
> I request you to kindly send me snapshots or blogs which has snapsot for this scenario.
>
No need of split 997 in outbound case. In this case, you will send the 810 and the partner will send the 997.
So, to receive that 997 file, you need another scenario. You need the split 997 communication channel only in inbound case like in 850, but not in outbound case.
> Last point -- is Dispatch advice direction is like 850 (Inbound ) or its direction is like 810 (outbound)?
> Do we have IDOC or something like that present and its mapping ?
>
like I said earlier, it is an outbound document if your company is the vendor.
It will be inbound if your company is the Customer to some other company.
The IDOC that is used usually will be DESADV idoc.
> Regards

Album View and Cover Flow View are not available in iTunes 7

Hi,
When I connect my iPod, in the iTunes 7, the options for Album view and Cover Flow View are disabled for the song list on my iPod. I only have a list view for them. However, at the same time, the songs on the library can be viewed in any of the three (3) views.
What might be the possible reason and is there any options to view your iPod songs in Cover Flow View in iTunes (while it is connected)?
Please solve this query of mine.

It just simply not a feature. You might think about requesting it here:
http://www.apple.com/feedback/itunesapp.html

Blurry/Scaled Down Artwork Column and Cover Flow are in 9.2

i have noticed on my iMac 27" that the album artwork is really blurry, and when i double click the art work at the left bottom and enlarge it, it looks fine. For some reason Apple scales down the pixel size of images and it looks really blurry. Before it was the standard 600x600 artwork that looked beautiful but not anymore..
This is an infuriating problem as I have taken a lot of time to embed high res art in my fles. The art still remains hi res in the bottom left, but in cover flow or the album artwork column it is a crappy looking blurry image.

I noticed this also. And yes, it infuriates me too. I used to browse my music collection in Cover Flow on a 46" LCD. Not any more since iTunes 9.2. iTunes 9.2 comes with several new features and improvements, including this one: "Album Artwork improvements make artwork appear more quickly when exploring your library".
It turns out that the album artwork cache build by iTunes consists of scaled down copies with a size of 128x128!!! These scaled down copies are used in the album artwork column, grid view, and cover flow. Not much you can do about it except give feedback (http://www.apple.com/feedback/itunesapp.html). That's what I did.

Creation inpayment agreements and cash flow to a loan account in banking

Hi,
I am using bapi "BAPI_BCA_INPAYMENT_AGR_CHANGE" to create inpayment agreements and cashflow to a loan account. It is updaing inpayment agrrement and cash flow table properly but the issue is it is not updating the first screen of the cashflow tab in loan account. This screen contains Cash flow key figures and Dated final payment.
Please let em know the solution to update the cashflow screen with bapi.
Thanks in advance
Regards
Shoban

Hi Shoban,
I am also trying to use the BAPI BAPI_BCA_INPAYMENT_AGR_CHANGE but get a messge back saying I should Open Brackets for the Contract.
How did you get past this error?
Did you manage to get the cash flow to re-calculate?
Shaun.

SD and MM FLOW with example

Hi friends,
Can any one tell me the SD and MM Flow with respect to company and customer like what the company and customer will do in various stages?

hai Reddy,
SAP Sales and Distribution Processing Document Flow
Document Flow in Sales
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
The following graphic shows how the various types of sales documents are inter-related and how data subsequently flows into shipping and billing documents.
D Transaction Code Flow:
Inquiry / Document type IN
Tcode for creation VA11,VA12, VA13. Tables VBAK, VBAP
Quotation / QT
Tcode for creation VA21,VA22,VA23. Tables VBAK, VBAP
Purchase Order PO
Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.
Sales Order OR
Tcode for creation VA01,VA02,VA03. Tables VBAK,VBAP
Delivery LF
Tcode for creation VL01,VL02,VL03. Tables LIKP,LIPS
Billing MN
Tcode for creation VF01,VF02,VF03. Tables VBRK,VBRP
To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no.
To create vendor tcode is
xk01(create), xk02(change) , xk03(display)
Tables are lfa1.
To create custmer tcode is xd01, xd02, xd03.
Table is kna1.
After creating sales order using this no we can create delivery note tcode is vl01.
MM FLOW.
Tables
PO
EKKO---Header level
EKPO-Item level
PR
EBAN
GR/Material document
MKPF--Header
MSEG-Item
Invoice
RBKP-header
RSEG-Item
Accounting doc
BKPF--header
BSEG--Item
ServicesSSR--Header
ESLL-Item
It really depends on the company and their business process. Generally though:
Purchase Requisition (user reqests stuff, either for manuf/stock, or supplies). -> then the PReq would go through an approval process (Release Strategy). Once approved, one can either create a Request for Quote (RFQ) to multiple vendors to obtain the best prices - and/or create the Purchase Order (either directly from the PReq or from the RFQ).
Once the PO is created -> then a Goods Receipt is necessary (to indicate you received the goods ordered). Then Invoice Verification (again - if this is set up) - which basically prevents overpayment to a vendor (won't allow you to pay for goods not received through Goods Receipt). Then ultimately the payment to the Vendor.
So - Transaction flow for create (common):
PReq -> RFQ -> PO -> G/R -> Invoice -> payment (?)
ME51N -> ME41 -> ME21N -> MIGO -> MIRO -> payment (?)
Tables for Purchase Requisition:
EBAN -
EBKN - Account Assignment
Tables for Purchase Orders:
EKKO - Header
EKPO - Item
EINA - Purchasing Info Record (oops forgot to mention that above - PInfoRec has the vendor/material/price for future sourcing)
Tables for Request for Quote:
same as PO above
Tables for Goods Receipt:
MKPF - Material Document Header
MSEG - Material Document Item
EKBE - History of PO
Tables for Invoice Verification:
BSIS (good substitute for BSEG, which is a monster)
If Found Helpfull Do Reward.
Regards.
EShwar.

EDI 940 and 945 Flow

Similar Messages

Maybe you are looking for