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

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.

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

HCM Form and Process ERROR No error agents maintained in table T5ASRERRORAG

Hi All,
I am setting up HCM form and Process and I am done with Setting up new scenario and form and workflow steps. When I do the check consistency for Processes I get these 4 error below and not sure what do i do about these error
No error agents maintained in table T5ASRERRORAGENTS
Case type for Step Object H_SO is not defined
Case type for Scenario Obj. H_FO is not defined
Case type for Process Object H_PO is not defined
Any help will be appreciated.
Thanks,
-Ashwani

Some elaboration would help here a LOT! Would it be possible to get some more info about it?
I am following this tutorial: http://help.sap.com/saphelp_erp60/helpdata/EN/42/f273461e5132c3e10000000a1553f6/frameset.htm
and didn´t find any "sub-chapters" about this. am I missing something? Or could you tell me the number of the tutorial step which I performed in a wrong way or did NOT performed?
Thank you, cheers Otto

Error while maintaining a table in SM30

Hi experts,
Im getting the following error when trying to add entries (Maintain) in table T5ASRAUTHMETHOD in SM30 transaction.
The error is " The maintenance dialog foor T5ASRAUTHMETHOD is incomplete or not defined".
Pls tell me how to correct this error.

Hi Shanthi,
the Delivery Class, and the existence of a tablemaintenance dialog,
and the "recording routine" setting. All of this would
be visible through SE11.
Regards,
Md Ziauddin

Maintaining the mapping information and writing update routine to populate

Hi,
Its my requriment to get the transactional data from r/3, here in the transaction data i will get the data in following format
(for example)
Material no.   Sales value    quantity ..
M001              100           2
M002              200           4
M003              150           3
now my requirement is to take the quantity per material number and multiply it with a factor called as SBU factor
.. my problem is that this SBU factor is not maintained in r/3 means the mapping information of material no. with its relative SBU factor is not maintained. So i thought of two option as this mapping is fixed means it will not changed so we can maintain in bw system through 1) one time upload of flat file or
2) maintaning a table in BW with mapping
so users agreed to give the mapping information as follows
Material no.    SBU factor
M001              5
M002              10
M003              7
now while uplading the transational data i need to take the SBU factor per material that is maintained through flat file or table and multiply it with quantity and store it quantity.
for example(the result i need in cube)
material no.   sales value    quantity(quantity * SBU)
M001             100           2*5=10
M002             200           4*10=40
M003             150           3*7=21
so i can do this at two level at transfer rules or update rules.
I need following clarification
1) shall i load the mapping information through flat file or maintain it in table?
2) If i will do the transformation at update rules so wht routine (start or update) should i write to get the SBU factor per material and do transformations
If possible send the sample routine.
Pls reply ASAP.
Thanks
Saleem.

Hi Saleem,
Nimesh is right..Do the multiplication in the Update rules.
If the data for this SBU factor is less and is always fixed, you can go for one time upload, else set up a RFC Call to load this data to BW from R/3 if no datasource for the same exist.
Else you can also maintain a table in BW, in which one time upload could be done by writing an ABAP, or manually. And then you can provide authorizsation to add more values to it, so that the table can be maintained.
And then in Update rules, use the table for look up and get the SBU Factor per material.
Some thing like
Select * from the <ODS table or Table name> into <internal table>
Loop at Data_Package.
Read table <internal table> for all values in Data_Package where internal table-Material = Data_package-MAterial.
If sy-subrc = 0.
Sales Value = Sales Value * internal table-SBU Factor.
ENDIF.
MODIFY DATA_PACKAGE.
ENDLOOP.
You might need to make more changes to this code as required.
Assign points if useful
Regards
Rohit

How can I maintain two tables content at the same time with SM30

Hi all,
I created two customizing tables that I would like to link together for maintenance in SM30. Table 1 is the header and table 2 can have multiple detail records.
They are linked via the ID key field. I would like to run the Table Maintenance Generator on the first table in SE11 and be able to maintain both table data at the same time in SM30.
How can I do that without any ABAP programming? Should I use Append or Include structure or else?
Thank you for giving as much detail as possible.
Regards,
Sylvain

Hi,
You cant do it w/t abap programing.
You can code in "EVENT" to achive the same.
Open table maintainance generator of first table through se56 or se11.
follow the path: environment>Modification>Event.
Select sutaible event from drop down like Before Save... and do coding.
In this way data will be saved in second table automatically when you save in first table.
In case of any query, please revert.
regards,
Dhan

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

Insert value to field automatically when maintaining db table

Hi,
I am maintaining Z table in sm30.
The first field is the material code and the second field is the material description (and there are other fields).
The requirement is inserting the description of the material automatically after inserting manually the material code.
How can this requirement be implemented ?
Best Regards.
Ofir

Use event No 5 In table maintenance generator.
Table maintenance Generator -> Environment -> Modification -> Events -> New entries => select event no 5. & do required coding
Regards
Vinod
Edited by: Vinod Kumar on Apr 21, 2010 5:26 PM

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.

Lock object for table KNVP and KNVK

Hello Friends,
Can you please tell me the standard lock object for the table KNVP and KNVK.
Thank and regards,
Kuldeep

Hi
see this and do accordingly
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
- Read Lock(Shared Locked)
protects read access to an object. The read lock allows other transactions read access but not write access to
the locked area of the table
- Write Lock(exclusive lock)
protects write access to an object. The write lock allows other transactions neither read nor write access to
the locked area of the table.
- Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
You have to use these function module in your program.
check this link for example.
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
tables:vbak.
call function 'ENQUEUE_EZLOCK3'
exporting
mode_vbak = 'E'
mandt = sy-mandt
vbeln = vbak-vbeln
X_VBELN = ' '
_SCOPE = '2'
_WAIT = ' '
_COLLECT = ' '
EXCEPTIONS
FOREIGN_LOCK = 1
SYSTEM_FAILURE = 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.
Normally ABAPers will create the Lock objects, because we know when to lock and how to lock and where to lock the Object then after completing our updations we unlock the Objects in the Tables
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
purpose: If multiple user try to access a database object, inconsistency may occer. To avoid that inconsistency and to let multiple user give the accessibility of the database objects the locking mechanism is used.
Steps: first we create a loc object in se11 . Suppose for a table mara. It will create two functional module.:
1. enque_lockobject
1. deque_lockobject
before updating any table first we lock the table by calling enque_lockobject fm and then after updating we release the lock by deque_lockobject.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
GO TO SE11
Select the radio button "Lock object"..
Give the name starts with EZ or EY..
Example: EYTEST
Press Create button..
Give the short description..
Example: Lock object for table ZTABLE..
In the tables tab..Give the table name..
Example: ZTABLE
Save and generate..
Your lock object is now created..You can see the LOCK MODULES..
In the menu ..GOTO -> LOCK MODULES..There you can see the ENQUEUE and DEQUEUE function
Lock objects:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
Match Code Objects:
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm
http://searchsap.techtarget.com/tip/0,289483,sid21_gci553386,00.html
See this link:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
Check these links -
lock objects
Lock Objects
Lock Objects
Regards
Anji

Value based Permit in maintainance order at release and Technical Completio

Hi All,
We have used value based permit in maintainance order at the time of release as well as technical completion, So presently if an order is having a planned cost of greater than 25000 say Rs 30000 , then at the time of release system is asking for permit.
After execution and confirmation of order if the actual cost is same i.e Rs 30000 then at the time of technical completion the system is asking for permit again which is shouldnt happen, please check for example below,
We have used classification in permit using table 'CSEVPERMIT' and field 'PKOSTEN' for planned cost of order and field 'IKOSTEN'
for actual cost, Permit shall be called for planned cost and actual cost greater than 25000.
EG :
order 'A' Planned cost = Rs 30000 Permit is called at release - (Correct)
Same order 'A' Actual cost = Rs 30000 Permit is called at Technical Completion - (Incorrect and to be avoided)
Solution Expected :
If for order 'A', once the permit is called at release then it should not call for Permit for the second time at Technical Completion if Planned and actual cost is same.
Thanks in Advance,

Hi,
1. I would suggest you to use separate set of Permits for Planned costs and Actual costs ..
For Actual cost permits in IPMD put Order completion as 02
For Planned Cost permits in IPMD put Order release as 02
2. If u have used same permits then in IPMD for Order Completion do not enter anything
If ur looking something different then check User exit :-IWO10007 Maint.order: Customer enhancement - permits in the order
regards
pushpa

How to maintain cluster table A016 -- Contract Item?

Hello,
I know Me11~ME13 can maintain info record for A017/A018, but how to maintain A016?
Thanks a lot

For Sched.aggrement, When you create ME31L, and enter the net price then save, go to EKKO table , get the condition number (EKKO-KNUMV), then go to table KONV and enter the doc.condition number, there you can see all the condition amount.

Date delimit functionality when maintaining Z table

Hi all,
I have Begin date and End date fields in a Z table and i want to achieve automatic date delimit functionality.
So i have the subscreen area in my screen and called a std program and screen inside the subscreen. I have writen the below coding in the PBO event of my screen.
MODULE DATE_D0001_IF_EXP.
CALL SUBSCREEN DATELIMITS INCLUDING 'SAPLSVIM' '0001'.
" DATELIMITS - name of my subscreen
But when maintaining the table in SM30, the BEGDA and ENDDA field headings are displayed. But those date input fields are not getting displayed.
Can someone tell me why the date fields from the std program, screen are not displayed inside my screen?
Edited by: Shanthi on May 2, 2011 1:59 PM

Hi,
There are some imports being done in the program for screen 0001. Based on these values, the screen fields are made visible and invisible etc.
IMPORT d0001_field_tab
         d0001_status
         x_header TO xheader
         current_date
         date_to_delimit
         date_to_posit
         vim_begdate_name
         vim_enddate_name
    FROM MEMORY ID vim_memory_id_2.
So try doing your validation with the events available in table maintenance,.
Regards,
Harish

How to update tables T156M and T156S

Hello,
In my company, there are a few custom movement types that were created sometime back. There is another custom program which uses the tables T156, T156M, T156S to determine, quantity addition or removal in a particular inventory status depending on the movement types and quantity strings.
The problem is that these tables do not contain the entries for the new movement types, hence the program cannot interpret whether to add or remove quantity and in which inventory status, for these new movement types.
Can someone please let me know a standard SAP program which we can run, in order to update these tables, so that these tables contain entries for the new custom movement types. I am not comfortable with maintaining the entries in these tables manually.
Thanks a lot for any help.

Hello Mahesh,
I appreciate your reply, but I have already checked the OSS notes section. I could not find anything which would help me. Hence, I posted the thread. I would appreciate if you can help me here. Thanks.
The note that you recommended, I had already checked, but that note only mentioned what needs to be maintained in the table, not how to maintain it. I mean, I know I can manually maintain entries, but I don't want to do it, unless it is the only option. Hence, I am looking for a standard SAP program, which when executed, will pull the information from OMJJ and update the tables T156M and T156S.
Hope you can help further on this. Thank you very much for your help.

Maintain HR table: TWPC_OBJSEL and TWPC_OBJSELRULE

Similar Messages

Maybe you are looking for