Maintain tables v_t521b and v_521c_b payee keys in production enviroment

One of our clients has requested as to open tables v_t521b and v_521c_b in the production enviroment to create and maintain payee keys for garnishees and court orders in south african payroll. Is this advisable or not because if these tables are open up by basis, then everything would be open for changes.

Hi Frik ,
This can be done for some production issues. BASIS people can give access for that particular table or view alone for a particular id.
Based on the roles provided for that id, tables can be maintained. 
Thanks & Regards,
Ganesh R K

Similar Messages

  • How to maintain table t180v and t180z

    hi all,
    when we customized va05 by copying it to zva05, SAP system prompt to maintain entry in both t180v and t180z. please advise the proper way to do that. thanks.

    Just sharing for the benefit of everyone.
    I had a similar issue when I was running an SD transaction VA45 for list of Contracts for Material and a Customer combination.
    The error message read "Please maintain an entry in Table T180Z." However I was not sure what entry had to be maintained. I debugged to see what entry was missing and then I was not sure how to maintain an entry in that Table. TCode OVBE is for Table 180V and in SM30 you can maintain T180V because it was a view table.
    Finally I was able to find transaction VXKP for maintaining the entry in table T180Z. This is where you maintain a default layout too.

  • Creation of Account payee keys and Table for House Bank

    Hi Gurus,
    Please tell me how to create a Account payee keys what is transaction code for this.And let me know that what is table to check the house Banks.
    Thanks

    I dont think you create payee keys mate, you get that data from your financial institute(bank) and then upload it into your sap system.
    so if I were in your position I would talk to the business user who deals with the bank & bank transfers currently in your client-organisation and ask for that info to be provided.
    from my previous payroll expreience I know the business user for payroll, usually the payroll manager, gets that info for the sap team member and then there should also be a standard upload program to upload all those payee keys into the system.
    cheers

  • Key fields in tables ce31000 and ce41000

    In transaction KE11 ( change sales and profit plan ), tables CE31000 and CE41000 are used. I have to read those tables in a report but I cannot find the relevant keys to find unique records.  There are some fields I know, but using those fields I get about 300 records where I only should have one.  I guess I should use another table which has the link to the other tables, but I have no idea which.  Does anybody have a clue ?

    As far as I remember there are 4 tables per operating concern, CE1xxxx for tha actuals, CE2xxxx for the planning, CE3xxxx for the summary lines and CE4xxxx for the objects.
    Depending on the defined characteristics there is one PAOBJNR in CE4xxxx for each existing combination. In CE3xxxx you should also find this PAOBJNR. At the moment I have no access to a SAP with COPA, but I hope, this helps you a little bit for the further search.
    Best regards
    André

  • Updation of Primary Key field in HR Tables (PA2001 and PA2002) - Urgent

    Can anyone please tell me how to update a primary key field in HR Tables (PA2001 and PA2002).
    I need to update sprps field in both the tables. I used HR_Infotype_Operation function module, but still it is not updating the field.
    Pls find the following code snippet for the table PA2001 and let me know if any discrepancies :
    TABLES: pa2001.
    DATA: it_pa2001 TYPE TABLE OF pa2001,
    wa_pa2001 LIKE LINE OF it_pa2001,
    DATA: date TYPE d.
    date = sy-datum - 100.
    SELECT pernr sprps begda endda FROM PA2001 INTO CORRESPONDING FIELDS OF TABLE it_pa2001
    WHERE begda BETWEEN date and sy-datum.
    WRITE:/.
    WRITE:/ 'PA 2001 Records'.
    if sy-subrc <> 0.
    WRITE:/ 'No Data Exists'.
    else.
    LOOP AT it_pa2001 INTO wa_pa2001.
    WRITE:/ wa_pa2001-pernr, wa_pa2001-sprps, wa_pa2001-begda, wa_pa2001-endda.
    ENDLOOP.
    endif.
    LOOP AT it_pa2001 INTO wa_pa2001.
    wa_pa2001-sprps = 'X'.
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
    infty = '2001'
    number = wa_pa2001-pernr
    SUBTYPE =
    OBJECTID =
    LOCKINDICATOR =
    VALIDITYEND =
    VALIDITYBEGIN =
    RECORDNUMBER =
    record = wa_pa2001
    operation = 'MOD'
    TCLAS = 'A'
    DIALOG_MODE = '0'
    NOCOMMIT =
    VIEW_IDENTIFIER =
    SECONDARY_RECORD =
    IMPORTING
    RETURN =
    KEY =
    ENDLOOP.
    if sy-subrc = 0.
    write:/ 'SY-subrc is zero'.
    write:/ ' Rows modified = ', sy-dbcnt.
    else.
    write:/ 'No Record(s) updated'.
    endif.
    commit work.
    WRITE: / 'Updated Records in the Internal Table IT_PA2001'.
    SELECT pernr sprps begda endda FROM PA2001 INTO CORRESPONDING FIELDS OF TABLE it_pa2001
    WHERE begda BETWEEN date AND sy-datum..
    LOOP AT it_pa2001 INTO wa_pa2001.
    WRITE:/ wa_pa2001-pernr, wa_pa2001-sprps, wa_pa2001-begda, wa_pa2001-endda.
    ENDLOOP.

    Thanks Kiran.
    But I need to change this field as we need to lock the records, as soon as the employee fills his/her time sheets which will be sent for HR Payroll, later on.
    When I am updating directly the field the database table PA2001, its not updating but for table PA2002, only few records are being updated.
    Is there any other alternative for this problem?
    Pls reply.
    Thanks,
    Harish

  • Find the key for join between table "crhd" and "equi" for use field "answt"

    I make program for read data from table "crhd" for print  about machine report
    but I can not find the key for link join to table "equi" for print field "answt" (acquistion value)
    please help me  find the key field for join between table "crhd" and "equi" for use field "answt"
    thank you very much...

    This is how the Work Center is linked to a particular Equipment -
    Functional - In IE03 ( view Equipments) You see the Work Center of a particular Equipment.
    Technical - Go to view V_EQUI ( view of EQUI and EQUZ). Pass the Equipment number alongwith V_EQUI-PM_OBJTY = 'A' ( i,.e searching for the Object Type Work Center).  In this way u ll get the V_EQUI-GEWRK - this is the Work Center ID.
    You can pass this Work Center ID to CRHD. And you will get the Work Center text.
    CRHD-OBJTY = 'A'
    CRHD-OBJID = V_EQUI-GEWRK.
    and u ll get the CRHD-ARBPL - this is the Work Center.
    So u need to come backwards, alongwith ur CRHD-OBJTY and CRHD-OBJID , you pass the same to V_EQUI and u get the list of equipment numbers alongwith ur ANSWT(Acquisition value).
    I guess it solves ur problem.

  • How to transfer database table contain null values, primary key, and foreign key to the another database in same server. using INSERT method.

    how to transfer database table contain null values, primary key, and foreign key to the another database in same server. using INSERT method.  thanks

    INSERT targetdb.dbo.tbl (col1, col2, col3, ...)
       SELECT col1, col2, col3, ...
       FROM   sourcedb.dbo.tbl
    Or what is your question really about? Since you talke about foreign keys etc, I suspect that you want to transfer the entire table definition, but you cannot do that with an INSERT statement.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Maintain HR table: TWPC_OBJSEL and TWPC_OBJSELRULE

    Hi experts,
    I tried to maintain these HR tables ( TWPC_OBJSEL and TWPC_OBJSELRULE ) by SM30 but failed.
    Could you please suggest me how to maintain these tables?
    Thanks,
    Khanh

    Hi Rahul Ghosh,
    V_TWPC_OBJSEL and
    VC_TWPC_OBJSELRULE
    Thanks,
    Khanh

  • Validity table for a Non-Cumulative key figure

    Hi,
    I need to make changes to a validity table for a Non-Cumulative key figure.
    I know initially it is done thru Extras- > Maintain Non-Cumulative value but subsequently how to change the parameters ?
    Best Regards,
    -Anurag Dev

    If you decide later that you require more validity-determining characteristics, you can modify the selection using the report RSDG_CUBE_VALT_MODIFY. In this report, the non-cumulative InfoCube is only changed to the extent that the new validity-determining characteristics are selected and the validity table is reconstructed. The structure of the non-cumulative InfoCube remains the same. You do not have to reload the transaction data for it.

  • Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

    Good day to all of you!
    I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
    In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
    I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
    MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
    1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
    2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
    PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
    All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
    Any help, pls?
    Good day and thank you!

    Hi Alex,
    In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
    http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
    and
    Just read the OSS note mentioned earlier.
    Symptom
    You want to integrate customer-specific fields in material master maintenance.
    Other terms
    SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001 
    Solution
    To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
          1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as  the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
          2. Enhancing online maintenance in customized material master maintenance:
          Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
          In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
          If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F): 
          Application examples for standard field selection:
          The field is mandatory and is to be flagged with a "?".
          The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
          The following data is required for each field:
                a) Field name        (T130F-FNAME)
                b) Field selection group (T130F-FGRUP)
                Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
                You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
                Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
                c) Maintenance status (T130F-PSTAT)
                List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
                d) Reference        (T130F-KZREF)
                This indicator must be set if the field from the reference material should be proposed during creation with reference.
    Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
    You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
    In addition, you must not add new standard fields to table T130F.
          3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
          Add the fields to central field table T130F (see above).
          Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
          Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
          For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
          If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
          Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
          As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
                a) Add the customer-specific fields to include CI_MMH1.
                The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
                Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in  table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
                b) Activate include CI_MMH1.
                c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
                d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
    Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
    In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
    Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
    If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
    If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
    To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
    check this link. It may helps you to solve your issue.
    Thanks
    Sravan

  • Vendor Evaluation data in tables ELBM and ELBP

    Hello,
    Please can someone provide some direction for this issue we have with MM Vendor Evaluation in ECC5.0.
    Basically, I have set up SAP standard Vend Evaluation config for our companies Purchase Orgs in SPRO, however, tables ELBM, and ELBP are not storing any values. The config that I have maintained includes:
    -     Define the weighting keys in SM30 - V_T147J : set to equal weightings
    -     Define the criteria in SM30 - V_T147G: left as standard
    -     Define the scope of list in SM30 - V_T147M: left as standard
    -     Define Purchasing Organization data: left as standard but no Subcriterion maintained. Weightings set as equal weightings. Points scores also left as standard/
    Any ideas?
    Thank you.
    Dave
    FL,USA.

    Once you do all the config than you have to use ME61 than use ME6H transaction.

  • Table maintenance and transaction

    HI ABAPERS
    Iam created one ztable in that fields are
      CLIENT like MANDT   PRIMARY KEY
      KUNNR like KUNNR   PRIMARY KEY
      MATNR like MATNR   PRIMARY KEY
      ERSDA like ERSDA       Created On
      ERNAM like ERNAm   Name of Person
      LAEDA like LAEDA        Date of Last Change
      AENAM like AENAm   Name of Person Who Changed t
    and iam maintaind settings as fallowes
    Data class: 'APPL0'  
    Size category: '1'      
    Delivery Class: 'A'
    Data Browser/Table view Maint: Display/maintenance allowed with restrictions 
    and i have this conditions
    - Create Maintenance view to maintain Z_SD_CUST_MAT database table using SM30
    - Assign transaction code 'ZCUSTMAT' to maintain table entries
    - Information like Created by, changed by  ERSDA, ERNAM, LAEDA, AENAM should be Display
    only and should be populated by the system at the time of data maintenance.
    how can i display only this four fields and in the table maitainence genarateor what Authorization Group i have to use.

    Hi, since you are in the table maintainence , all the non-key fields will be enabled mode. If you want these fields to be in display mode,  make them key fields.
    But why do you want to have these fields disabled when  accessing through sm30?  You may as well use se11 or se16 to view the data .
    Edited by: Srini Bhagavatam on Aug 21, 2008 12:36 PM

  • Need to know alternative country Key and Vehicle country Key

    Hi Experts,
    I am defining new country codes in SAP ECC and GTS System. Can someone help me to find out Alternative country key and Vehicle country key for the below mentioned country Codes.
    AX
    Åland Islands
    GG
    Guernsey
    IM
    Isle Of Man
    JE
    Jersey
    PS
    Palestinian Territory, Occupied
    TL
    Timor-Leste
    Please assist me in this regard as this is very urgent.
    Thank you
    Vinod Kakarla

    Hi,
    Use Tcode - VI78 to find alternative country key
    T coe - OY01 for vehicle country key
    001 (European standard formatting), 002 (Italy), 011 (Switzerland) and 014 (Austria) use the vehicle country key of the relevant country. If no vehicle country key has been maintained in Customizing, the country key of table T005 is used instead. If, for the sender country, the indicator for printing the country name in foreign addresses is set in table T005 , the system does not use the country key, but generally prints the country name in the last address line. Check the sap Note: 1509425.
    Ashish

  • I want to write condition while creating table/maintaining table using SM30

    Hello all,
    I am creating table Z_CUST with only 2 fields Client, Customer number using SE11 transcation then maintain using SM30 transcation.
    User should only be allowed to enter customer number that is in account group(KNA1-KTOKD) ‘Z011’. This  validation should be performed during data entry.

    Hi,
    Crete the table maintenance generator for your Ztable.
    below is the brief procedure to create table maintenance.
    Table maintenance generator is basically used to do table operations like (insert, delete, modify...).
    if you create table maintenance for your table it will build a module pool program, by using you do the above operations.
    below is the procedure to create table maintenance generator.
    1) Create one function group.
    2) after activating your Ztable, choose 'Utilities'----> 'Table maintenance genrator'.
    3) then give the authorization group and function group created abobe in the next screen.
    4) Then choose the "create" button in your application tool bar, which will creates the module pool program.
    5) then create one Tcode by chosing "Transaction with parameters( parameter transaction)".
    6) in transaction field give "SM30", select the check box "Skip initial screen".
    7) in the below of that screen you can find the "Default values" frame.
    8) there under the "name of screen field" select the "View name' and 'update".
    9) in value column against to "view name" give you table name, and against to "Update" put 'X' in capital letters.
    save it then you can straight away use this newly created Tcode to maintain your table.
    Note:- 1) make the modification while saving the data into your table using this newly generated program to carry out your validation (even though it looks like standard program; no need to enter the access key).
    2) if you do any changes to your table and press the activate button automatically the table maintenace generator will be goes off, you need to create this again.
    Reward if useful.
    Thanks,
    Sreeram.

  • Composite selection groups in step "Maintain table reduction" ?

    Hello forum,
    I have a table ZMCHA that I want to filter in the same way as the standard MCHA (I am talking about TDTCC here).
    MCHA is filtered with selection group G_WERKS (you can see that in table CNVMBTCOBJ).
    I wanted to apply this selection group to ZMCHA in step "Maintain table reduction", but from what I see you can only apply "simple" selection groups in the transaction, not "composite" selection groups (in CNVMBTSELGRPDEF you can see that G_WERKS = G_WE + G_WE_SP; I can apply G_WE or G_WE_SP in the transaction, but not both).
    I did manage to apply G_WERKS by changing tables CNVMBTCOBJ and CNVMBTSELREF directly, but would it be possible to do it in the normal transaction? Am I missing something?
    Another related question: in that same transaction, if want to choose "no transfer" for a given table I have to double click it, the system will try to find possible selection groups (which takes some seconds) and then I choose no transfer. Obviously, if I want to choose "no transfer" there's no need for the system to determine the possible selection groups, and avoiding that would make the configuration much faster. Again, am I missing something in the transaction, or is the best option to go directly to CNVMBTCOBJ and forget that transaction?
    Hope I was clear,
    Thanks in advance for any help,
    Rui Dantas

    >
    Surmeet Singh Lamba wrote:
    > It is possible to assign a complex selection group to one object provided the structure of two objects i.e. standard and the 'Z' table created is same.
    > In case you are not able to do so, i would request you to raise an OSS message for the same and TDMS team will definetely help you to solve this issue.
    Hi Surmeet,
    Sorry for taking so long to answer, but I had to create a new package to be able to reproduce the problem.
    I have a ZMCHA table with the same key fields as MCHA. I would like to have it reduced in the same way that MCHA is.
    If I check table CNVMBTCOBJ I can see that MCHA is reduced with selection group G_WERKS (that is, G_WE + G_WE_SP).
    If I try to reduce ZMCHA via the screen then both G_WE and G_WE_SP appear as options, but G_WERKS does not.
    In fact, G_WERKS doesn't appear in the screen even if I select the standard MCHA
    (and, by the way, the transaction will show G_WE_SP as selected for MCHA, and then change the value in CNVMBTCOBJ to G_WE_SP even if I don't save the assignment, which I would say is a bug).
    I just wanted to confirm if we are talking about the same thing. If yes, and if this should work, I will open an OSS message.
    Thanks in advance,
    Rui Dantas

Maybe you are looking for