Inbound IDoc(HRMD_A07) problem in delimiting the infotype records

Hi All,
I am using Inbound IDoc (HRMD_A07) approach to update infotypes. I found that I am able to create a record in an infotype, but there is a problem in delimiting the infotype.
Please help me out in case I am missing something.
Thanks,
ABAP_DEV

Hi,
Did you get this resolved. Even i'm facing this issue. Is it a config or do we have to do something in the IDOC.
Thanks,
Jilly

Similar Messages

FM for delimit the infotype record

Hi
I'm new to HR-ABAP.I need to develop function modules to delimit the some infotype records (eg: 0167,0168,0014,2006 etc)
Presently i developed the function module that has following source code.
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
    EXPORTING
      number        = empno
CALL FUNCTION 'HR_READ_INFOTYPE'
    EXPORTING
     tclas                 = 'A'
      pernr                 = empno
      infty                 = '0167'
      begda                 = delimitdate
      endda                 = delimitdate
BYPASS_BUFFER         = ' '
LEGACY_MODE           = ' '
IMPORTING
SUBRC                 =
    TABLES
      infty_tab             = itab "itab is of the structure p0167
enddate = itab-endda.
MOVE delimitdate TO itab-endda.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
      infty                  = '0167'
      number                 = empno
      subtype                = itab-subty
      objectid               = itab-objps
      lockindicator          = itab-sprps
      validityend            = enddate
      validitybegin          = itab-begda
      recordnumber           = itab-seqnr
      record                 = itab
      operation              = 'LIS9'
      tclas                  = 'A'
      dialog_mode            = '0'
NOCOMMIT               =
VIEW_IDENTIFIER        =
SECONDARY_RECORD       =
   IMPORTING
     return                 = return
KEY                    =
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
    EXPORTING
      number        = empno
when i use 'MOD' operation in FM 'HR_INFOTYPE_OPERATION' that FM runs perfectly.it changes the enddate to delimit date in the table PA0167.
But, when i use 'LIS9' (delimiting) operation FM is throwing following error message
"E PG 428 A complex application error has occurred".
I need help regarding this error statement.can i use 'MOD' operation to delimit the records (time constraint of most of the infotype record to be delimited is 2).In which case we use 'LIS9'??
Also any SAP function modules for delimiting IT2006 infotypes????
Pls suggest.
Thank u,
shrinivas
Message was edited by: Shrinivas

For 167 & 168 have you looked at HR_BEN_TERMINATE_HEALTH_PLAN & HR_BEN_TERMINATE_INSURE_PLAN?
The error message you got is actually mapped to (00)344 ie "No batch input data for screen & &"
For the delimit operation, you probably,need to pass the delimit date separately..
I have a feeling this function call cannot be used for the delimit operation le 'LIS9'.AS the delimit date is usually entered on a pop-up box when you do it via PA30.
~Suresh

Captivate 8 Tin Can - problem communicating with the learning record store

When publishing a course to Tin Can format, what should I enter in the 'Identifier' field?
If I publish with the default 'Course_ID1' text, I get an error when launching the course on our LMS. Errors says "There was a problem communicating with the learning record store."

Hello,
Welcome to Adobe Forums.
Please share your contact information via [email protected]
Thanks,
Vikram Gaur
Adobe Support

Position 1000001 not available for the start date of the infotype record

Dear Experts/Gurus,
I am getting the following error message "Position 1000001 not available for the start date of the infotype record" while trying to upload employees HR Master data in PA40.
I know the reason why because the position is created on 01.05.2009 & employee DOJ is 01.02.2006 both are mismatch & the position date has to be changed earlier date than DOJ but i don't know how to do.
Please let me know how to sort out this issue asap.
Rgds,
Vikrant

Dear Friend,
Use PP02, select the position no, select infotype 1000 (Object), select planning status & validity(date) and then use the copy function to change the start date.
Regards,
Aks

Problem in delimiting the Relationship

Hi,
When we try to create a create a new relationship using PP01 for a Org. Unit, it is not delimiting the existing relationship. It just creates another relationship. But for some of SAP Standard relationships when i try to create the new relationship it automatically delimits the existing relationship. Whats wrong with my Z relationship. Why it is not delimiting the existing relationship.
Appreciate your help!
Thanks,
-Suresh Revuru

hI,
Double click on your relationship category in transaction BUBA and assign proper time constraint.
Thanks and warm regards,
Smita.

Problem in creating 0027 infotype record in background

Hi Experts,
I am facing the problem in creating 27(Costs distribution) infotype record in back ground.
Whenever there is a change in position of the employee or when we hire a new employee (Through PA40)
i have to ctreate 0027 infotype record in background.For that i am using IN_UPDATE method of BADI
HRPAD00INFTY.
Here i am getting 2 problems.
1. I am unable to get the latest positions that is assigned to the employee.
Through NEW_IM AGE structure we can get the latest position but if a person is assigned to multiple positions for the same period then i am getting only one position from NEW_IM AGE but not all.can any body help me?
2. I am calling HR_INFOTYPE_OPERATION FM to create the IT0027 record in background in the above method (IN_UPDATE). but it is not updating the PA0027 table. any idea?
Full points will be rewarded.
Regards,
Sai.

I am sending a sample program , which is on infotype 0105 (communication). I hope that this program will help u out............
REPORT ZSAPHR_SAMP.
tables: pa0105.
infotypes: 0105.
DATA : I_RETURN TYPE BAPIRETURN1,
I_KEY TYPE BAPIPAKEY,
PERNR TYPE P0001-PERNR,
I_P0105 TYPE TABLE OF P0105 WITH HEADER LINE,
ENDDA TYPE P0105-ENDDA,
BEGDA TYPE P0105-BEGDA.
MOVE '00000010' TO PERNR.
BEGDA = SY-DATUM + 1.
ENDDA = SY-DATUM + 1.
i_p0105-pernr = PERNR.
i_p0105-infty = '0105'.
i_p0105-subty = '0002'.
i_p0105-endda = ENDDA.
i_p0105-begda = BEGDA.
I_P0105-USRTY = '0002'.
I_P0105-USRID = '[email protected]'.
APPEND i_p0105.
CALL FUNCTION 'DEQUEUE_ALL' .
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
EXPORTING
NUMBER = PERNR.
IF SY-SUBRC = 0.
WRITE 'Employee Locked Successfully'.
ENDIF.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
INFTY = '0105'
NUMBER = PERNR
SUBTYPE = '0002'
VALIDITYEND = BEGDA
VALIDITYBEGIN = ENDDA
RECORD = i_p0105
OPERATION = 'INS'
TCLAS = 'A'
DIALOG_MODE = '0'
NOCOMMIT = 'X'
IMPORTING
RETURN = I_RETURN
KEY = I_KEY.
IF SY-SUBRC = 0.
WRITE : 'FM returns sy-subrc 0'.
ENDIF.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
EXPORTING

Problem in modifying the existing record in table control

Hi Experts,
I have one table control.I have entered one record and save it.When I am modifying the same record a duplicate record is created.I need if I modify the same record that record should only modify.How to delete the duplicate record.

Hi,
In Flow logic.
LOOP .
MODULE tbc_modify ON CHAIN-REQUEST.
MODULE tbc_mark.
ENDLOOP.
In module.
MODULE tbc_modify INPUT.
MODIFY t_data
    FROM fs_data
   INDEX tbc-current_line.
IF sy-subrc NE 0.
    APPEND fs_data TO t_data.
ENDIF.
ENDMODULE.
MODULE tbc_mark INPUT.
DATA: tbc_wa2 LIKE LINE OF t_data.
IF tbc-line_sel_mode = 1
AND fs_data-mark = 'X'.
    LOOP AT t_data INTO tbc_wa2
     WHERE mark = 'X'.
      tbc_wa2-mark = ''.
      MODIFY t_data
        FROM tbc_wa2
        TRANSPORTING mark.
    ENDLOOP.                          .
ENDIF.
MODIFY t_data FROM fs_data
    INDEX tbc-current_line
    TRANSPORTING mark.
ENDMODULE.
Edited by: sapabap403 on Aug 31, 2011 9:29 AM

Mandatory fields for inbound - idoc HRMD_A07

Hi All,
I need to create an Employee master record in R/3 by triggering an idoc .
i came to know ,i can use "HRMD_A07" .
can any one help me giving the mandatory datas to trigger the HRMD_A07.
Thanks & Regards,
Arun

Hi,
PA objects exist if infotypes 0000, 0001, and 0003 have been created.
So fill the segment accordingly, but I am not sure whether you can directly create the employee from Idoc, you may have to take the Idoc option of LSMW.
Br/Manas

Inbound IDOC basic type HRMD_A07: Why no validation available?

I am using a standard inbound IDOC basic type HRMD_A07 to update employee master data (IT0000 & IT0001). However, i found out that this IDOC just directly updates to the infotypes without any validation. For example, i provide an invalid company code (BUKRS) and personnel area (WERKS), the IDOC still updates into database without any proper validation.
Filled the following fields in the IDOC segments:
E1PLOGI
plvar=01, otype=P, objid=00000001, opera=I
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0000, begda=20120101, endda=99991231
E1P0000
pernr=00000001, infty=0000, endda=99991231, begda=20120101, massn=01, massg=01, stat1=3, stat2=3
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0001, begda=20120101, endda=99991231
E1P0001
pernr=00000001, infty=0001, endda=99991231, begda=20120101, bukrs=XXXX, werks=XXXX, persg=1, persk=EC, abkrs=99, plans=00000111, otype=S
Please help me out in case I am missing something. Thanks.

Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel

Inbound IDOC for sales orders not posting the configuration data

Hi all,
I am facing a problem in posting the inbound IDOC (message type ORDERS). The configuration data maintained in the parent segment E1CUCFG and in the segment E1CUVAL is not getting posted though i am passing the data in these segments which is 100% correct.
Can any one solve this problem

Hi Ravi,
Please check the two segments are active. You can do that in BD53.
In BD53 enter message type, and make the segments active.
If segments are active, it appears in white colour.
After this post the IDoc and check with segments.
If its useful, award points pls..
Regards,
Bharadwaj

Inbound - IDoc problem

Hi Friends,
Can anybody help me . I am facing a problem in IDOC inbound processing.
My scenario in SALES PER RECEIPT - POS like this: I have to read XML (From PC) file and i have to post it.
I am using Idoc - WPUBON01. After reading XML file i used Function module to distribute - MASTER_IDOC_DSTRIBUTE.
In we02 i checked Idoc is generating but status showing 29.
So run the report RSEOUT00. But i am getting message like 'No idoc is selected for processing'.
Plz help me what i have to do. I created port also.
Regards,
P. Kumar.

Hi,
sarath has told valid point..don't use master_idoc_distribute,instead use the bapi
bapi_idoc_input1..
plz check the sample code how to do with inbound idoc,as u have got the data ,u just need to call the bapi and post it..
check the code and proceed..
FUNCTION zdtsint052f_gpoms_to_sap_gm.
""Local interface:
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
Purpose            :On recording the material consumption from       *
                    manufacturing tickets in GPOMS system, GPOMS     *
                    will report the data to the SAP system.Based     *
                    on this message, goods issue to the process order*
                    will be posted in SAP. This interface will       *
                    used for storage location managed materials      *
                    in SAP.                                          *
Program Logic      :Loop at the data records of IDOC and to get the *
                    Order number and SAP Movement type               *
                    If the Material document already exists for this *
                    Order number and Movement type then give error   *
                    else call standard FM 'BAPI_IDOC_INPUT1' to      *
                    Material Documents in SAP.                       *
Declaration of Constants                                             *
CONSTANTS :lc_item_create(25) TYPE c VALUE 'E1BP2017_GM_ITEM_CREATE',
             lc_mbgmcr(6)       TYPE c VALUE 'MBGMCR'.
Declaration of Variables                                             *
DATA : lv_index TYPE sytabix,
         lv_retcode type sy-subrc.
Declaration of Workareas                                             *
DATA: lwa_e1bp2017_gm_item_create TYPE e1bp2017_gm_item_create,
        lwa_data         TYPE edidd, " Work area for IDOC
        lwa_control      TYPE edidc. " Work Area for control rec
Read the control data information of idoc.
loop at idoc_contrl INTO lwa_control Where mestyp = lc_mbgmcr.
Extract the data from the segments.
    LOOP AT idoc_data INTO lwa_data
    WHERE docnum = lwa_control-docnum and
          segnam = lc_item_create.
*->> Set the tabix of the internal table
      lv_index = sy-tabix.
Move the Material Document Item Segment data
      MOVE lwa_data-sdata TO lwa_e1bp2017_gm_item_create.
Modify the material document item data internal table
      PERFORM sub_modify_idocdata changing lwa_e1bp2017_gm_item_create.
*->> set the changed values to the IDOC SDATA
      MOVE lwa_e1bp2017_gm_item_create TO lwa_data-sdata.
*->> Modify the table
      MODIFY idoc_data FROM lwa_data index lv_index.
Clear the Work areas
      CLEAR : lwa_data,
              lwa_e1bp2017_gm_item_create.
    ENDLOOP.                                     "LOOP AT t_idoc_data
Call the BAPI function module to create the
appropriate Material Document
    CALL FUNCTION 'BAPI_IDOC_INPUT1'
      EXPORTING
        input_method          = input_method
        mass_processing       = mass_processing
      IMPORTING
        workflow_result       = workflow_result
        application_variable = application_variable
        in_update_task        = in_update_task
        call_transaction_done = call_transaction_done
      TABLES
        idoc_contrl           = idoc_contrl
        idoc_data             = idoc_data
        idoc_status           = idoc_status
        return_variables      = return_variables
        serialization_info    = serialization_info
      EXCEPTIONS
        wrong_function_called = 1
        OTHERS                = 2.
    IF sy-subrc = 1.
      RAISE wrong_function_called.
    ENDIF.
endloop.
ENDFUNCTION.
***INCLUDE LZDTSINT052F_GPOMS_GMF01 .
*&      Form sub_modify_idocdata
Modify the material document item data internal table
FORM sub_modify_idocdata
CHANGING pwa_e1bp2017_gm_item_create TYPE e1bp2017_gm_item_create.
contant declaration
CONSTANTS: lc_261(3) TYPE c VALUE '261'.
DATA : lv_aplzl LIKE resb-aplzl,
         lv_aufpl LIKE resb-aufpl,
         lv_subrc LIKE sy-subrc,
         lv_charg LIKE resb-charg,
         lv_uom LIKE pwa_e1bp2017_gm_item_create-entry_uom.
CLEAR: pwa_e1bp2017_gm_item_create-reserv_no,
         pwa_e1bp2017_gm_item_create-res_item.
*->> Get SAP storage bin & Storage type from the Z table
SELECT lgtyp lgpla
    INTO (pwa_e1bp2017_gm_item_create-stge_type,
          pwa_e1bp2017_gm_item_create-stge_bin)
     UP TO 1 ROWS
    FROM zdtsint050_sttyp
     WHERE zstorage_typ = pwa_e1bp2017_gm_item_create-stge_type
      AND zstorage_bin = pwa_e1bp2017_gm_item_create-stge_bin.
ENDSELECT.
IF sy-subrc NE 0.
    CLEAR: pwa_e1bp2017_gm_item_create-stge_type,
           pwa_e1bp2017_gm_item_create-stge_bin.
ENDIF.
PERFORM get_oper CHANGING pwa_e1bp2017_gm_item_create.
Get the Reservation number and Reservation item number
basing on the idoc data.
SELECT rspos werks lgort
         INTO (pwa_e1bp2017_gm_item_create-res_item,
              pwa_e1bp2017_gm_item_create-plant,
                 pwa_e1bp2017_gm_item_create-stge_loc)
         FROM resb
         UP TO 1 ROWS
         WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no
         AND   matnr = pwa_e1bp2017_gm_item_create-material
         AND   charg = pwa_e1bp2017_gm_item_create-batch
         AND   aufnr = pwa_e1bp2017_gm_item_create-orderid
         AND   vornr = pwa_e1bp2017_gm_item_create-activity
         AND   bwart = lc_261.
ENDSELECT.
IF sy-subrc <> 0.
Start of insertion for R31K993797
    CLEAR lv_charg.
    SELECT rspos werks lgort
         INTO (pwa_e1bp2017_gm_item_create-res_item,
              pwa_e1bp2017_gm_item_create-plant,
                 pwa_e1bp2017_gm_item_create-stge_loc)
         FROM resb
         UP TO 1 ROWS
         WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no
         AND   matnr = pwa_e1bp2017_gm_item_create-material
         AND   charg = lv_charg
         AND   aufnr = pwa_e1bp2017_gm_item_create-orderid
         AND   vornr = pwa_e1bp2017_gm_item_create-activity
         AND   ( splkz = 'X' or
                 splkz = space )
         AND   bwart = lc_261.
    ENDSELECT.
    IF sy-subrc <> 0.
End of insertion for R31K993797
      SELECT SINGLE werks lgort
            INTO (pwa_e1bp2017_gm_item_create-plant,
                   pwa_e1bp2017_gm_item_create-stge_loc)
            FROM resb
            WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no.
      CLEAR : pwa_e1bp2017_gm_item_create-reserv_no,
              pwa_e1bp2017_gm_item_create-res_item.
    ENDIF.
ENDIF.
get SAP UOM
SELECT SINGLE zsap_uom
                INTO lv_uom
                FROM zca_uom_conv
                WHERE zext_uom = pwa_e1bp2017_gm_item_create-entry_uom.
IF sy-subrc = 0.
    pwa_e1bp2017_gm_item_create-entry_uom = lv_uom.
ENDIF.
ENDFORM.                    " sub_modify_idocdata
*&      Form get_oper
     Get the operation
     <--P_PWA_E1BP2017_GM_ITEM_CREATE_RE Segment
FORM get_oper CHANGING p_pwa_e1bp2017_gm_item_create TYPE
               e1bp2017_gm_item_create.
DATA : l_aufpl LIKE afko-aufpl,
         l_aplzl LIKE afvc-aplzl.
REFRESH : i_op.
UNPACK p_pwa_e1bp2017_gm_item_create-orderid TO
         p_pwa_e1bp2017_gm_item_create-orderid.
Get the reservation and routing number for the order
SELECT SINGLE
         rsnum
         aufpl
         FROM afko
         INTO (p_pwa_e1bp2017_gm_item_create-reserv_no,
               l_aufpl)
         WHERE aufnr = p_pwa_e1bp2017_gm_item_create-orderid.
IF sy-subrc = 0.
    CALL FUNCTION 'CONVERSION_EXIT_NUMCV_INPUT'
      EXPORTING
        input = p_pwa_e1bp2017_gm_item_create-activity
      IMPORTING
        output = p_pwa_e1bp2017_gm_item_create-activity.
ENDIF.
ENDFORM.                    " get_oper
i have modifeid the incoming data,in ur case its not needed ,only first few lines until the bapi u have to see..if u have any query let me know..
Regards,
Nagaraj

What is the standard inbound idoc for substation management?

Hello Experts,
Can anybody help me to find out the standard inbound idoc for substation management?
The following field are requied to be filled in idoc.
1)Power_Produced(STAGR)
2) Reduction_Power_Consumed(STAGR)
3)Ancillary_Power_Consumed (STAGR)
4)Unit (MEINB)
5) UOM and Date (BUDAT)
If possible please tell me the standard BAPI for these fileds.
Thanks in advance for your help.
Thanks and Regards,
Suresh.

Hi Debo,
What is your exact requirement?
Are you trying to find the standard configurations available for a webdynpro application? then, use t-code SE15 and open the application name and use the tree structure to find out the available configurations under WD application.
sample:
Regards,
Rama

NO MATERIALs in the Sales order created through inbound idoc file

hi,
i have maintained the customer material number as well the SAP Material number in the tcode VD51,but still the inbound
idoc type ORDERS03 is posting the application document(Sales order) without the materials.
for instance,
I have cust.material as CUSTMAT1 in the idoc file.
I have maintained the CUSTMAT1 as cust material and 1001 as material no in VD51.
After posting the inbound idoc file using RSEINB00 prg,the idoc is created and i can see the CUSTMAT1 in the material segment field
The Sales order is created successfully ,but without the materials.
i need the application document has to be posted with materialsm,can any one help me to solve this issue.?
Thanks

Hi ganesh ram
In order to determine the Material Number with you custom material then you needs to have some configurations.
Check with your Functional consultant to add the Access sequence for determining the Material Number with you custom material
In Sale order processes...
Thanks
Ramesh

When i am running the RBDMDOC it will not genarated the idoc for the infotype 0105

               Hi experts,
                        I am run a pa40 action and change the record of 0105 infotype, in bd64 as part of data filtering I am also mentioned 0105 . but when I am run the RBDMIDOC the idoc is not generated of the infotype 0105 .
Thanks in Advance .
Venkateswara Rao.

Hi Venkat Narayan,
   Thank for giving such a help,
1.   I am created record for the infotypes i.e :0,1,2,6,105.
2    In bd64 I done a data filtering for above infotypes , its fine , but when I am running the bd21   Tcode the idoc is generated for    0,1, 2,6,. it is not generated for p0105.
     please find the following screen shorts.
Thanks.
venkat

Creation of Sales Order and Service Contract from Inbound IDOC

Hi Experts,
My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
Thanks in Advance.
Regards,
Priyabrata

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

Inbound IDoc(HRMD_A07) problem in delimiting the infotype records

Similar Messages

Maybe you are looking for