PO Output message types for different document types

Hi,
I wanted the system automatically generate the messages whenever a PO is created for different document types like NB,UB,Blanketorder, Pilot run.
These are the steps i did...plz advice any more steps to make this work
1. the output type I am using is NEU-purchase order
2. I have created condition records for document types NB,UB,PR etc
I was sucessfull in getting the messages automatically for the standard(NB) PO..but not for the other document types
Plz advice me how I can achieve this with further configurations
Thanks
SKid

If you have created conditin record for all the document type in MN04 then it should work becuase doc type has nothing to do for printing config.
this is basically a condition record.
check your condition record

Similar Messages

How can I combine profiles for different document types ?

Hello, we work with SAP basis 6.40 and we have several different documents set up in DMS. We want to allow users to see only selected app. files depending on the document type. Let me set an example:
DOKAR = ZDT only .pdf (profile name DMS_ZDT)
DOKAR = ZCS only .doc and .xls (profile name DMS_ZCS)
We created 2 profiles and assigned them to 2 roles.
The user with both roles who enter in the CV03N will see only .pdf files regardless of the DOKAR.
Is there some way to obtain a different filter based on the document type ?
Thank you,
Vincenzo Lucarelli

Dear Mr. Lucarelli,
based on your description I think the responsible function module is 'CV119_GET_USER_PROFILE'.
Due to information from our development team it is recommended to assign only one role to one user or profile. For further information you an see also the Online documentation. Due to this fact that function module only keep in mind one profile and does not take into account the second one.
Please consider following scenario as an example:
User 1 -> Role A -> Profile A
-> Role B -> Profile B
"User 1" will not be able to use all the profiles.
This is according to the logic in FM CV119_GET_USER_PROFILE.
As per the documentation in the customizing of DMS for profiles there is a recommendation that recommends to assign only one role to a user or activity group. So I think that the single profiles should be assigned directly to the user and not by using a role.
Best regards,
Christoph

Output Message Setup for Material Document

Hi,
Can you guide me on setting the default output message for 101 Documents.
Regards
Shankar

Hi,
PRINT OUT OF MATERIAL DOCUMENT :
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
2. Ensured in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
3. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, maintain the Output device for all your Plants
7. In MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.(Condition records)
8. While doing MIGO, ensured that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
Now go to MB90 entered the output type as WE01, Tr m as 1, Sort or. 01, Pro.mode as 01, and executed. Sytem outputted all the material documents that has to be taken print out.
Regards,
Shailesh Mackwan

Output for PO document type

I have created 4 document types in PO
Domestic, Import, Service, Subcontracting,
I have to add extra one document type and i want the print out of this document type should be different from remaining 4
only for this 5th document type i need to have different output..
Is it possible in SAP

Hi,
You should have different document types for all process( Domestic, Import, Service, Subcontracting and 5th one) and can have one output type for all document type ( where you have one SmartForm) OR you can have different output types( five SmartForm ) for each document type.Just talk to ABAPer for inclusion of all PO output formats with all condition types.
Regards,
Biju K

How to add a default user group for multiple document type's?

Hi,
I am trying to add same default user group for different document types when MA is created. Is there any way to setup using a single "Document Security Template"? Or I need to create different templates for different document types?
Please confirm.
Thanks,
Saloni

Hi Saloni,
Based on what your specific requirement, it might be easier to do it with scripting.
If you are doing it using Document Security Templates, you would have to create a Document Security Template for each of the 6 MA types and assign the default group. Create another one and leave the Document Type field blank, so it will apply to the other 4 MA types that don't have a default group.
Regards,
Vikram

Can we have different output types for same document?

Hi,
Can we have different output types for same doucument.if yes plz describe the steps to perform it
Thanks

Hi,
Generally you can use same out put type for the different document types of PO. You can create different out put types for the same PO, in case you need different layouts that is different forms like MEDRUCK. Please refer below link to create out types . If you want that PO as fax or e-mail can use same out put type .Thanking you.
http://www.sap-img.com/materials/purchasing-tips.htm

Different Document Type for a standard transaction

Dear all,
Iu2019m facing the following problem: I wish to set a different Document Type for a standard transaction.
In the specific, I need a different DT for Reverse Document (T-code FB08) instead of standard SA.
Is that possible?
Thanks in advance
Alberto

Go to OBA7, click on doc type of the original document (which I guess is SA) and then update the field "Reverse Doc Type" to the doc type you want to.

Multiple Document Types For Purchase Requisition For Different Order Types

Dear SAP Gurus,
I want to have different document types of Purchase Requisition for different Order types.
For Example:
for Order Type ZT01- Document Type used should be YR01
for Order Type YA01- Document Type used should be ZR01
How could this be achieved?
Regards.

hi
Kindly check the user exit for the same
COZF0001 or COZF0002
regards
thyagarajan

Different Document types for Reciepts and payment-Cash Journal

Hi Gurus,
Please tell me how can we make different document types for reciepts and payments in cash journal and where we need to assign it??
Please revert asap.
Thank You

Hi
While posting the transactions by using FBCJ T.Code u can select the Receipts or Payments or Expenses then the documents will be genereted. FBCJ02 is the T.Code for no.range there u can assign the no.range intervels.
Shammi

GR output quantity for different material types using 101 mvt

Hi All
Is it possible to have separate GR slip quantities for the same movement type (101) but for different stock types.
I would like 3 GR slips for mvt type 101 for directly procured materials AND
I would like 1 GR slip for mvt type 101 for stock materials
Therefore, the material type on goods receipt would decide how many GR slips would be printed.
What config is necessary?
Thanks in advance
Darren

material type is fixed for a material, it is not changed for GR.
you can make no of GRs or one po.
for stock items you need to make one PO and matrial for account assignment need separete PO.
account assignment PO > material direclty goes to cost center and consumption accouont
no configuration required.

Uploading data in MM01 for different material types

Hi,
I have a doubt regarding uploading the data in MM01 for different material types.
Generally in MM01, we have different views for different material types. The number of views will vary depending upon the material type that we select.
I have a scenario, where in to upload the data, I have a flat file that consists of data for different message types. So, how to upload the data in such case.
Can anyone help me on the same by providing explanation or sample code...? What would be the possible ways to upload data in such scenario.
That would be of great help.
Thanks & Regards,
Pradeep.

See the below code and use FM SELECTION_VIEWS_FIND..
REPORT zjpmuim306 NO STANDARD PAGE HEADING LINE-SIZE 250 MESSAGE-ID
zjpm001.
*&   I N B O U N D V I A   A B A P : Batch input Session method     *
*&   Development ID: IM_DD_306_LJP                                   *
*&   Report        : ZJPMUIM306                                      *
*&   The Purpose of the Object is to interface Create Input Record   *
*&   for SAP Migration from the Material master of BPCS All the      *
*&   information received at BPCS is collected into a single record. *
*&   By using session method upload data from file ,one item is
*&   created for one record                                          *
*&   Change Log:                                                     *
*&   Init       Who              Date         Text                   *
*& MALIKDH1   Seshu Reddy    26-07-2003   Initial Version           *
                         Constants                                   *
CONSTANTS:c_vkorg(4) type c value 'JP20',        " Sales Organization
          c_vtweg(2) type c value 'TR' ,         " Distribution Channel
          c_werks(4) Type c value 'JP01' ,       " Plant
          c_viewlist(15) VALUE 'KDEALBSZXVPCFQG'," View list
          c_scm_view TYPE msichtausw-dytxt VALUE 'SCM View',
          c_sd_view TYPE msichtausw-dytxt VALUE 'SD View',
          c_seq_code(2) VALUE 'Z1',              " Sequential Code
          c_keep(1) TYPE c VALUE 'X',           " Keep
          c_group LIKE apqi-groupid VALUE 'IM306', " Session Name
          c_tcode LIKE tstc-tcode VALUE 'MM02', " Transaction Code
          c_blank(1) VALUE ' ',                   " Blank
          c_intls(1) VALUE 'N'.                  " Logistic Status
              Variables                                      *
DATA: g_flag1(1), " Variable to hold
      g_flag(1),   " Variable to hold
      g_file LIKE rlgrap-filename VALUE
     'C:\Documents and Settings\seshur\Desktop\HCLT123.CSV'. " File name
       Internal tables/ Work area                           *
Internal Table for Delimter
DATA : BEGIN OF t_delim OCCURS 0,
       text(1000),
       END OF t_delim.
Internal table for BDC processing
DATA : t_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
Internal table for holding the data which has to be uploaded.
DATA: BEGIN OF t_bpcs OCCURS 0,
      matnr(15) TYPE c, " material no
      dosage(40) TYPE c, " Dosage form(Local)
      appearance(40) TYPE c, " Appearance
      idcode(6) TYPE c,     " Identification Code
      prostformno(10) TYPE c, "SOP
      weitab(7) TYPE c,    " Weight/tablet
      uom1(2) TYPE c,     " UOM of Carton
      uom2(2) TYPE c,     " UOM of Case
      carsize(14) TYPE c, " Carton size
      cassize(14) TYPE c, " Case size
      rupqty(11) TYPE c, " Round up
      abvname(3) TYPE c, " Product short name
      END OF t_bpcs.
*Internal table for t_bpcs
DATA: BEGIN OF t_mdata OCCURS 0,
      matnr LIKE marc-matnr, " Material number
      zzjp_dos_frm LIKE marc-zzjp_dos_frm, " Dosage form(Local)
      zzjp_aprn LIKE marc-zzjp_aprn, " Appearance
      zzjp_con_id LIKE marc-zzjp_con_id," Identification Code
      zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,"SOP
      zzjp_wei_tab(10) type c , " Weight/tablet
      zzjp_bio LIKE marc-zzjp_bio,"Biologics Indicator
      zzjp_itf LIKE marc-zzjp_itf, " ITF code
      zzjp_car(2) type c, " UOM of Carton
      zzjp_cas(2) type c, " UOM of Case
      zzjp_car_size(11) type c," Carton size
      zzjp_cas_size(11) type c, " Case size
      zzjp_rupqty(11) type c, " Round up
      zzjp_init_ls LIKE marc-zzjp_init_ls, " Logistic Status
      zzjp_re1 LIKE marc-zzjp_re1, "Document type(Local)
      zzjp_re2 LIKE marc-zzjp_re2, "Report type
      zzjp_re3 LIKE marc-zzjp_re3, "Shipping report type
      zzjp_pro_id LIKE mvke-zzjp_pro_id," Product output sequence
      zzjp_bu_id LIKE mvke-zzjp_bu_id, " Business unit indicator
      zzjp_abv_name LIKE mvke-zzjp_abv_name," Product short name
      zzjp_abv_id1 LIKE mvke-zzjp_abv_id1," Product short name output
      zzjp_abv_id2 LIKE mvke-zzjp_abv_id2," Product short name internal
      zzjp_spl_id LIKE mvke-zzjp_spl_id, " Sample internal order
      END OF t_mdata.
Internal table for Mara Table
DATA: BEGIN OF t_mara OCCURS 0,
      matnr LIKE mara-matnr, " material Number
      vpsta LIKE mara-vpsta, " Maintenance status of complete material
      pstat like mara-pstat, " Maintenance status
      END OF t_mara.
Internal table for Material Master View Selection Screens
DATA: BEGIN OF t_bildtab OCCURS 0.
        INCLUDE STRUCTURE mbildtab.
DATA: END OF t_bildtab.
internal table for T_bildtab
DATA: t_bildtab_dup LIKE t_bildtab OCCURS 0 WITH HEADER LINE.
*Work area for T_bildtab internal table(Views Selection)
DATA: BEGIN OF w_data,
      flag1 type c,
      anzd70 TYPE i,
      field1(20) type c,
      field2(20) type c,
      field3(20) type c,
      field4(20) type c,
      count(2) TYPE c,
      END OF w_data.
            Main Processing                           *
START-OF-SELECTION.
Store data from file into internal table
PERFORM f_uplaod_data.
Transfer the uploaded data into t_mdata internal Table
PERFORM f_process_data.
Selecting The views based on Material number
PERFORM f_view_list.
Open a BDC Session
PERFORM f_bdc_open.
*Selecting the fields from mara table
SELECT matnr
         vpsta
         pstat
    FROM mara
INTO TABLE t_mara
FOR ALL ENTRIES IN t_mdata
WHERE matnr = t_mdata-matnr.
SORT t_mara BY matnr.
SORT t_mdata BY matnr.
Transfer the uploaded data into BDCDATA structure
PERFORM f_process_bdc.
Close The BDC Session
PERFORM f_close_group.
*&      Form F_VIEW_LIST                                             *
         Routine to used for Calling the function module            *
          Selection_views_find                                      *
FORM f_view_list.
CALL FUNCTION 'SELECTION_VIEWS_FIND'
       EXPORTING
            bildsequenz     = c_seq_code
            pflegestatus    = c_viewlist
       TABLES
            bildtab         = t_bildtab
       EXCEPTIONS
            call_wrong      = 1
            empty_selection = 2
            OTHERS          = 3.
IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " F_VIEW_LIST
*&      Form f612_view_sort                                          *
Routine to used for Selecting The views based on Material Number *
FORM f612_view_sort.
t_bildtab_dup[] = t_bildtab[].
Reading the Internal table t_mara
READ TABLE t_mara WITH KEY matnr = t_mdata-matnr.
TRANSLATE t_mara-pstat USING ' $'.
CLEAR: w_data-flag1, w_data-anzd70.
LOOP AT t_bildtab_dup.
    IF t_bildtab_dup-pstat CA t_mara-pstat.
      w_data-anzd70 = w_data-anzd70 + 1.
      IF t_bildtab_dup-kzanz IS INITIAL.
        t_bildtab_dup-kzanz = 'X'.
        w_data-flag1 = 'X'.
        MODIFY t_bildtab_dup.
      ENDIF.
    ELSE.
      IF NOT t_bildtab_dup-kzanz IS INITIAL.
        CLEAR t_bildtab_dup-kzanz.
        w_data-flag1 = 'X'.
        MODIFY t_bildtab_dup.
      ENDIF.
    ENDIF.
ENDLOOP.
TRANSLATE t_mara-pstat USING '$ '.
IF NOT w_data-flag1 IS INITIAL.
    SORT t_bildtab_dup BY kzanz DESCENDING idxbd ASCENDING.
ENDIF.
*Reading The internal table for T_bildtab_dup
READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
IF t_bildtab_dup-kzanz = 'X'.
    WRITE sy-tabix TO w_data-count.
    w_data-count = w_data-count + 2.
    IF w_data-anzd70 > 18.
      w_data-count = w_data-count - 18.
    ENDIF.
    CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field1.
    CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field2.
ENDIF.
READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
IF t_bildtab_dup-kzanz = 'X'.
    WRITE sy-tabix TO w_data-count.
    IF w_data-anzd70 > 18.
          w_data-count = w_data-count + 2.
      w_data-count = w_data-count - 18.
    ENDIF.
    CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field3.
    CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field4.
ENDIF.
ENDFORM.                    " f612_view_sort
*&      Form f_uplaod_data                                           *
Routine to used for Uploading the data from file to Internal table *
FORM f_uplaod_data.
CALL FUNCTION 'WS_UPLOAD'
       EXPORTING
            filename                = g_file
            filetype                = 'DAT'
       TABLES
            data_tab                = t_delim
       EXCEPTIONS
            conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_type            = 4
            no_batch                = 5
            unknown_error           = 6
            invalid_table_width     = 7
            gui_refuse_filetransfer = 8
            customer_error          = 9
            OTHERS                  = 10.
IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF t_bpcs IS INITIAL.
    LOOP AT t_delim.
      SPLIT t_delim-text AT ',' INTO t_bpcs-matnr
                                     t_bpcs-dosage
                                     t_bpcs-appearance
                                     t_bpcs-idcode
                                     t_bpcs-prostformno
                                     t_bpcs-weitab
                                     t_bpcs-uom1
                                     t_bpcs-uom2
                                     t_bpcs-carsize
                                     t_bpcs-cassize
                                     t_bpcs-rupqty
                                     t_bpcs-abvname.
      APPEND t_bpcs.
    ENDLOOP.
ENDIF.
ENDFORM.                    " f_uplaod_data
*&      Form F_BDC_OPEN
      Routine to create BDC Session to be processed
FORM f_bdc_open.
CALL FUNCTION 'BDC_OPEN_GROUP'
       EXPORTING
            client              = sy-mandt
            group               = c_group
            keep                = c_keep
            user                = sy-uname
       EXCEPTIONS
            client_invalid      = 1
            destination_invalid = 2
            group_invalid       = 3
            group_is_locked     = 4
            holddate_invalid    = 5
            internal_error      = 6
            queue_error         = 7
            running             = 8
            system_lock_error   = 9
            user_invalid        = 10
            OTHERS              = 11.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
MESSAGE S000 WITH 'Batch input session is created successfully'(T02).
ENDIF.
ENDFORM.                    " F_BDC_OPEN
*&      Form F_PROCESS_BDC
      Processing of BDCDATA Structure
FORM f_process_bdc.
LOOP AT t_mdata.
    PERFORM f612_view_sort.
    PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0060'.
    PERFORM f_bdc_field USING 'BDC_CURSOR'
                                  'RMMG1-MATNR'.
    PERFORM f_bdc_field USING 'BDC_OKCODE'
                                  '=AUSW'.
    PERFORM f_bdc_field USING 'RMMG1-MATNR'
                                  t_mdata-matnr.
    PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
    PERFORM f_bdc_field USING 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(01)'.
    IF w_data-anzd70 > 18.
      PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                  '=P+'.
      PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0070'.
      PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
    ENDIF.
reading the t_bildtab internal table
    READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
    IF t_bildtab_dup-kzanz = 'X'.
      PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                    w_data-field1.
      PERFORM f_bdc_field       USING w_data-field2 'X'.
      g_flag = 'X'.
    ENDIF.
reading the t_bildtab internal table
    READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
    IF sy-subrc EQ 0.
      g_flag = 'X'.
    ENDIF.
    IF t_bildtab_dup-kzanz = 'X'.
      PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                    w_data-field3.
      PERFORM f_bdc_field       USING w_data-field4 'X'.
      g_flag1 = 'X'.
    ENDIF.
    IF g_flag = 'X' AND g_flag1 = 'X'.
      PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
      PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                    'RMMG1-VTWEG'.
      PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                    '=ENTR'.
      PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                    c_werks.
      PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                    c_vkorg.
      PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                    c_vtweg.
      CLEAR g_flag.
      CLEAR g_flag1.
    ELSE.
      IF g_flag = 'X'.
        PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
        PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                    c_werks.
        PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
      ELSE.
        IF g_flag1 = 'X'.
          PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
          PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                        'RMMG1-VTWEG'.
          PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                      c_werks.
          PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                        c_vkorg.
          PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                        c_vtweg.
          PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                         '=ENTR'.
        ENDIF.
      ENDIF.
    ENDIF.
*Processing of SCM View
    PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
    PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MARC-ZZJP_DOS_FRM'.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_DOS_FRM'
                                  t_mdata-zzjp_dos_frm.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_APRN'
                                  t_mdata-zzjp_aprn.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CON_ID'
                                  t_mdata-zzjp_con_id.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_NYU_SOP'
                                  t_mdata-zzjp_nyu_sop.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_WEI_TAB'
                                  t_mdata-zzjp_wei_tab.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR'
                                  t_mdata-zzjp_car.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS'
                                  t_mdata-zzjp_cas.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR_SIZE'
                                  t_mdata-ZZJP_CAR_SIZE.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS_SIZE'
                                  t_mdata-ZZJP_CAS_SIZE.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RUPQTY'
                                   t_mdata-ZZJP_RUPQTY.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_BIO'
                                  t_mdata-zzjp_bio.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_ITF'
                                  t_mdata-zzjp_itf.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_INIT_LS'
                                  t_mdata-zzjp_init_ls.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RE1'
                                  t_mdata-zzjp_re1.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RE2'
                                  t_mdata-zzjp_re2.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RE3'
                                  t_mdata-zzjp_re3.
    PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
*Processing of SD View
    PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
    PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MVKE-ZZJP_PRO_ID'.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_PRO_ID'
                                  t_mdata-zzjp_pro_id.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_BU_ID'
                                  t_mdata-zzjp_bu_id.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_NAME'
                                  t_mdata-zzjp_abv_name.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID1'
                                  t_mdata-zzjp_abv_id1.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID2'
                                  t_mdata-zzjp_abv_id2.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_SPL_ID'
                                  t_mdata-zzjp_spl_id.
    PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
    PERFORM f_bdc_dynpro      USING 'SAPLSPO1' '0300'.
    PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                  '=YES'.
perform f_bdc_insert.
REFRESH T_BDCDATA.
ENDLOOP.
ENDFORM.                    " F_PROCESS_BDC
*&      Form f_bdc_dynpro
p_prog is the program name to which data is passed                *
p_dyno is the screen number to which the data is passed
    Routine for populating the BDCDATA structure with the
    Screen related information
FORM f_bdc_dynpro USING    p_prog
                           p_dyno.
t_bdcdata-program = p_prog.
t_bdcdata-dynpro   = p_dyno.
t_bdcdata-dynbegin = 'X'.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM.                    " F_bdc_dynpro
*&      Form F_BDC_FIELD
      p_fnam is the field name to which value is passed
      p_fval is the field value which is passed
   p_fnam is the field name to which value is passed
   p_fval is the field value which is passed
FORM f_bdc_field USING    p_fnam
                          p_fval.
t_bdcdata-fnam = p_fnam.
t_bdcdata-fval = p_fval.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM.                    " F_bdc_field
*&      Form F_PROCESS_DATA                                          *
     Routine to used for moving data from T_bpcs internal table to *
     t_mdata Internal Table                                         *
FORM f_process_data.
LOOP AT t_bpcs.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
              input = t_bpcs-matnr
         IMPORTING
              output = t_mdata-matnr.
    MOVE t_bpcs-dosage TO t_mdata-zzjp_dos_frm.
    MOVE t_bpcs-appearance TO t_mdata-zzjp_aprn.
    MOVE t_bpcs-idcode TO t_mdata-zzjp_con_id.
    MOVE t_bpcs-prostformno TO t_mdata-zzjp_nyu_sop.
    MOVE t_bpcs-weitab TO t_mdata-zzjp_wei_tab.
    MOVE c_blank TO t_mdata-zzjp_bio.
    MOVE c_blank TO t_mdata-zzjp_itf.
    MOVE t_bpcs-uom1 TO t_mdata-zzjp_car.
    MOVE t_bpcs-uom2 TO t_mdata-zzjp_cas.
    MOVE t_bpcs-carsize TO t_mdata-zzjp_car_size.
    MOVE t_bpcs-cassize TO t_mdata-zzjp_cas_size.
    MOVE t_bpcs-rupqty TO t_mdata-zzjp_rupqty.
    MOVE c_intls TO t_mdata-zzjp_init_ls.
    MOVE c_blank TO t_mdata-zzjp_re1.
    MOVE c_blank TO t_mdata-zzjp_re2.
    MOVE c_blank TO t_mdata-zzjp_re3.
    MOVE c_blank TO t_mdata-zzjp_pro_id.
    MOVE c_blank TO t_mdata-zzjp_bu_id.
    MOVE t_bpcs-abvname TO t_mdata-zzjp_abv_name.
    MOVE c_blank TO t_mdata-zzjp_abv_id1.
    MOVE c_blank TO t_mdata-zzjp_abv_id2.
    MOVE c_blank TO t_mdata-zzjp_spl_id.
    APPEND t_mdata.
ENDLOOP.
ENDFORM.                    " F_PROCESS_DATA
*&      Form f_bdc_close
      Routine to close the BDC Session
FORM f_close_group.
CALL FUNCTION 'BDC_CLOSE_GROUP'
       EXCEPTIONS
            not_open    = 1
            queue_error = 2
            OTHERS      = 3.
IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " f_close_group
*&      Form f_bdc_insert
     routine to input batch data into the Transaction MM02 from the
     session created
FORM f_bdc_insert.
CALL FUNCTION 'BDC_INSERT'
         EXPORTING
              tcode            = c_tcode
         TABLES
              dynprotab        = t_bdcdata
         EXCEPTIONS
              internal_error   = 1
              not_open         = 2
              queue_error      = 3
              tcode_invalid    = 4
              printing_invalid = 5
              posting_invalid = 6
              OTHERS           = 7.
    IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDFORM.                    " f_bdc_insert
Reward Points if it is useful
Thanks
Seshu

Customs document type cannot be determined for external document Type F8

Hello Experts
Need help
I am trying to transfer F8 to GTS 10.1 and getting following message in GTS Transfer log for export:
Customs document type cannot be determined for external document Type F8
New implementation
GTS 10.1 running with SP 12
ECC side Plug-In settings are fine. BAdi is Active.(There is no document mapping for F8/CUSDEC as it is not required in 10.1)
GTS side configurations are also fine. Checked several times by 4 sets of eyes!!
(Include general settings configurations, Customs communication configurations:)
(Defining technical medium, conditions/output parameters, defining messages for communication process,
defining determination for activity sequence and control settings for communication process)
Despite this I am not able to trnasfer F8 successfully
Can someone throw some light on this issue please?
Keshav Murthy
[email protected]

Hi Dhilipan
Here we go..
You asked me to check the following
Please check following things
1) Legal regulation is activated. - Yes Activated
2) Process template assigned to the legal regulation - Yes Assigned
3) Activity Sequence determination - Yes done
4) Open the activity sequence in under Control settings for Communication processes and check if there is a document type assigned to it. Table- /SAPSLL/TLEPAF - Yes done.
It is really puzzling.
Thanks
Keshav Murthy

Vendor Payment with different document types

Dear Sapguru,
We have a scenario where a particular vendor payable is in two different document types for example, RE and KZ.
When we execute TC F110, the payment proposal is grouping the payments by document type. I.e. it grouped all the documents under type RE and grouped all the documents under type KZ and created two line items in the payment proposal.
Actually, we want to have a single group consisting of all the document types payable to the vendor.
We have checked different SAP notes and also verified out system settings, but the problem still remains.
Can somebody let us know how to group all the open items in a single line item in F110 irrespective of document types.
Thanks in Advance.
Regards.,
Rama

Dear Naravi,
the main factor which affects the grouping of items is the Structure ZHLG1:
ZBUKR
ABSBU
LIFNR
KUNNR
EMPFG
WAERS
ZLSCH
HBKID
HKTID
BVTYP
SRTGB
SRTBP
XINVE
PAYGR
UZAWE
DTWS1
DTWS2
DTWS3
DTWS4
KIDNO
All these fields have to coincide, to have a single payment.
Please check why two documents with different document type are paid into two different payments.
Read the SAP notes 109233 and 164835 and 305414 as well.
I hope this helps.
Mauri

Use of different document type in PO??

hii
Can some body explain me with their real time exp about the PO and PR document types necessary in SAP system.??
Because hope with creating new document types we can do all the Procurement type using NB ??
Then what will be need of custom document types for the same in SAP system??
Thanks
Edited by: MM group on Aug 2, 2010 1:56 PM

>
MM group wrote:
> hii
>
> Can some body explain me with their real time exp about the PO and PR document types necessary in SAP system.??
>
> Because hope with creating new document types we can do all the Procurement type using NB ??
>
> Then what will be need of custom document types for the same in SAP system??
>
> Thanks
>
> Edited by: MM group on Aug 2, 2010 1:56 PM
Usually the standard document types are enough, customized document types are required, when there is need of release strategies getting trigged for different departments, or different departments require their own document types e.g. document type created for mechanical, as ZMNB with release strategy for this document type going to head of mechanical,
document type ZENB for engineering where release strategy final release is HEAD OF ENGINEERING and so on and each document type can have there own number range and so on.

Two different document types in MIRO

Hi Gurus,
Can we have two different FI document types in MIRO for Service PO and Normal PO?
Standard is RE but we want one more.
Can you please suggest something?
Regards,

You can work with your own document types but I do not hink you can have two different document types for Standard and Service PO.
The effect of MIRO is still the same whether its Service PO or Standard PO - GR/IR debit and Vendor credit.
If it is just for reporting, you can always take the PO number from RSEG table.Then drill down to EKKO/EKPO and get all the details.

PO Output message types for different document types

Similar Messages

Maybe you are looking for