Creation of new Infotype Important

Hi All,
I am using the table control for my Infotype creation. i linked the internal table with the table control wizard. I added a check box in the table control ( which is not there in the internal table). i need to access this table control check box. how can i make it.
Do i need to include the check box value in it.
Please Kindly help me to solve this issue
Thanks
Yogesh.

it will be a complex logic as such... Instead try using the same in internal table so that u can use it in a simple code manner...
Award Points and close duplicate threads...

Similar Messages

Creation of NEW Infotype

Hello Experts,
I need to create new infotype ,which will be replica of Infotype-0008(basic pay). user can enter the wage types in that custom infotype.
is it possible????
Thanks & Regards,
Saurabh

"there are some employees who works extra apart from their regular position "
questions:
1. "there are some employees "--> do they have specific characteristic?
2. "who works extra apart from their regular position"-->
is the extra salary payment will be included in their regular payroll or will be paid separately or it is only to record the "extra work"? or
"work extra" is it a form like overtime payment?
if it will be included in the salary payment, you can create new wagetype and include it in in IT0014-IT0015 depends on the regularity of the payment.
"currently in custom infotype there is only limited information ie. position and pay scale area, groups n all and cost centers.."
did u mean "currently in IT0008" there is only limited info (position, pay scale area, groups ...)
please check or consider to use IT0014 and IT0015 -- sap standard infotypes for other extra payment not included in the Basic Pay.
best regards,
dhenny muliawaty (pei pei)

Creation of new infotype 9001

am trying to create the new infotype 9001 (PM01) for license but SAP not allowing.. asking access key to proceed further.. wot to do?
Shan

and also check this
Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the u2018Employee Infotypeu2019 radio button.
4) Select the u2018PS Structure Infotypeu2019.
5) Click on Createu2026 A separate table maintenance window appearsu2026
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on u2018Allu2019 push button. It takes a few moments.
10) Click on u2018Technical Characteristicsu2019. Infotype list screen appears
11) Click on u2018Changeu2019(pencil) button
12) Select your Infotype and click on u2018Detailu2019 (magnifying glass) button
13) Give u2018T591Au2019 as subtype table
14) Give u2018T591Su2019 as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on u2018Infotype Characteristicsu2019 u2026 Infotype list screen appears
18) Click on u2018Changeu2019 (pencil) button
19) Click on u2018New Entriesu2019
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotypeu2019s infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirementu2026
25) In the PM01 initial screenu2026Select u2018Screenu2019 radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select u2018Layout Editoru2019 and click u2018Changeu2019.
27) Screen default layout appearsu2026here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Donu2019t forget to u2018Activate at every level

Creation of new tab

Hi Guy's,
creation of new infotype we are using Transation code:PM01, when we enter this TS it displays differnt tabs like : Create infotype,infotype version, Screen structure.. presnt require ment is to enhance the one tab to that TS.(Ex: create the one custom infotype like Employee Details, when ever we press the Eployeedetails tab it displays the related field list). Pease help me how to proceed this senario.
Thanks and Regrads,
Sai.
Edited by: sai shanhu on Apr 7, 2008 8:44 AM

Sai shanhu,
Creating Infotypes for PA and PD using PM01.
1. Infotypes should be started between 9000 9999
2. Go to transaction code PM01.->select Create infotype
3. Give the Infotype number on the screen 9010
4. Click on the Button Generate Objects right to the Infotype input field.
5. It asks for the Creation of the PS9010 structure for infotype. Create, save and activate and come back remaining things will be created automatically. Remaining things means Module pool program, User interface, BADI.
6. Maintain infotype characteristics ex: Time constraints, Subtype, assigning single screen & list screen and save.
7. Select Screen radio button and give 2000 on input field and press edit button .It takes you to the SE51 screen painter. Here we have to write logic for the validations for the fields on the Infotype screen.
Creating subtypes for the infotype
1. Create subtype field in the PS structure of the infotype table.
2. Go to PM01 and press on technical attributes button and select infotype for which subtype should be maintained and display in change mode and enter Subtype field, T591A (Subtype table), T591T (Subtype text table), T591A (Time constraint table) tables and save and exit.
3. Go to SM30 and enter V_T591A and press maintain. Enter subtype numbers and its text and save.
I hope that it helps u .
Regards,
Venkat.O

About new infotype creation ?

Hi Experts,
I want to create new infotype in PD.
Will any one help me how to start with.
Before creating infotype whether we need to create structure.
How to create the structure HRI9xxx.
*Please give the step by step procedure and t-code to create theHRI9xxx structure,Pxxxx,any tables like T777 etc.
*Suggest some links to create these things.
*Give step by step procedure to create structure and Infotypes.
Helpfull answers are rewarded for sure.
Thanks,
Sakthi C

Steps to create a HR Infotype:
1) Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the 'Employee Infotype' radio button.
4) Select the 'PS Structure Infotype'.
5) Click on Create... A separate table maintenance window appears...
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on 'All' push button. It takes a few moments.
10) Click on 'Technical Characteristics'. Infotype list screen appears
11) Click on 'Change'(pencil) button
12) Select your Infotype and click on 'Detail' (magnifying glass) button
13) Give 'T591A' as subtype table
14) Give 'T591S' as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on 'Infotype Characteristics' ... Infotype list screen appears
18) Click on 'Change' (pencil) button
19) Click on 'New Entries'
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype's infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirement...
25) In the PM01 initial screen...Select 'Screen' radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select 'Layout Editor' and click 'Change'.
27) Screen default layout appears...here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Don't forget to 'Activate at every level)
Subtype Creation :
Transaction PM01 Goto Subtype Characteristics. Click on Append and then subtype. Enter the name and description of subtype on screen.
Then goto technical Characteristics and maintain the details of subtype there. I.e name of subtype i.e. component name defined in PSnnnn. Subtype table is T591A.
Subty.text tab is T591S and time const tab is T591A.
See:
http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
HR related site:
http://www.sapdevelopment.co.uk/hr/hrhome.htm
Enhancement of Infotype
Check the following
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_INFOTYP.pdf
Infotype Enhancement overview screen
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60a7586d-edd9-2910-68a8-8204303835a1
Reward points if uesful.

Creation of New fast entry for custom infotype

Hi all, I need to create new fast entry form my custom 9010 inft.
What I need to do,? How to create screen for input and how to assign it to transaction PA70.
Change some modules or what?
Kind regards.

to create a new infotype for personnel administration (PA) use transaction PM01.

Error in new infotype creation

hi,
i m copying a infotype and create a new infotype, in this all structures are copied in my program but only one structure q0002 is not copied as q9002 .
tell me how to do this

Hi
Just copy the Qnnnn structure for yourself via SE11,
I think it is not automatically copied, because it is not part of IT 02. It is only part of the display dynpro.
regards,
karl

Creation of new Sales order

Hi,
       While creating a new Sales Order(tcode VA01) depending on the material, Item category will be generated and depending on the Item category purchase requisition screen(ME51n) will be automatically opened and PR will be created.
Now to automate this process, BAPI_SALESORDER_CREATEFROMDAT1 will be called to create the sales order. But the requirement is that we need to pass Requisitioner and Vendor to the BAPI for creation of PR.
But in this BAPI there is no option/field to pass Requisitioner and Vendor. So is there any other BAPI/Function Module where a new Sales order is created and also we can pass Requisitioner and Vendor required for creation of new PR.

REPORT ZSALESORDER.
Parameters
Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
    header-COMPL_DLV = p_autlf.
    header-COMPL_DLV = 'X'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Fill schedule lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.

Getting ORA-20001: Creation of new object is not allowed: !!

Hi Am getting ORA-20001: Creation of new object is not allowed while enabling constraints after importing the dumps from source to target datbase,can anyone assist me to fix this issue.

Hi Osama/Mustafa,Thanks for your quick response,can you please explain me the following things-
1)As i don't have privilege to run the DBA_XX views,am not able to run those queries-
SELECT OWNER, TRIGGER_NAME, TRIGGER_BODY FROM DBA_TRIGGERS WHERE TRIGGER_TYPE IN ('AFTER EVENT', 'BEFORE EVETN') AND TRIGGERING_EVENT LIKE '%CREATE%';
can you tell me what output it'll throw,based on this output how will we fix the issue.
2)SELECT * FROM dba_sys_privs WHERE privilege = 'UNLIMITED TABLESPACE';
why we need to check this privilege?as i don't have privilege to run this one in my db.
3)select * from dba_source where upper(text) like upper('%Creation of new object is not allowed%');
as i don't have privilege to run this one in my db,already i got the object name from my logfile
and more you have quoted"This is an error of someone that coded purposely on your database, probably dba or a developer who has privilege and again it is in a database event trigger"
4)can you explain me much more deeper about the root cause and as already sent note to my DBA,can you explain me the solution to fix this issue ?

Creating new Infotype

I created a new infotype 9015. It works and posts correctly. Then I tried adding a module within the 9015 code to generate an infotype 0014. So the end result should be a 9015 and a 0014 record.   While Im in PA30 I can see the expected results but if I leave PA30 and come back in the records are gone. Looks like some type of commit issue but I have tried adding code to COMMIT and it doesnt help.
Here is the additional IT0014 code.
    move GV_RETIRE-wage_type_ee to gt_pa0014-SUBTY.
    move GV_RETIRE-wage_type_ee to gt_pa0014-LGART.
    move GV_RETIRE-ee_percent to gt_pa0014-ANZHL.
    move p9015-endda to gt_pa0014-endda.
    move p9015-begda to gt_pa0014-begda.
    move p9015-pernr to gt_pa0014-pernr.
    move '0014' to gt_pa0014-INFTY.
    Append gt_pa0014.
    CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
      EXPORTING
        NUMBER = p9015-pernr
      IMPORTING
        RETURN = gt_return.
   CALL FUNCTION 'BAPI_EMPLOYEET_ENQUEUE'
     EXPORTING
       NUMBER              = p9015-pernr
       VALIDITYBEGIN       = p9015-begda
    IMPORTING
      RETURN              = gt_return.
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        infty         = gt_pa0014-INFTY
        number        = gt_pa0014-pernr
        subtype       = gt_pa0014-subty
        validityend   = gt_pa0014-endda
        validitybegin = gt_pa0014-begda
        record        = gt_pa0014
        operation     = 'INS'
        tclas         = 'A'
        dialog_mode   = '0'
        nocommit      = ''
      IMPORTING
        return        = lstr_bapireturn
        key           = lstr_bapikey.
    IF NOT lstr_bapireturn-number = 0.
      lv_bapierror = lstr_bapireturn-message.
      lv_failed = abap_true.
    ENDIF.
       CALL FUNCTION 'BAPI_EMPLOYEET_DEQUEUE'
     EXPORTING
       NUMBER              = p9015-pernr
       VALIDITYBEGIN       = p9015-begda
    IMPORTING
      RETURN              = gt_return.
    CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'
      EXPORTING
        NUMBER = p9015-pernr
      IMPORTING
        RETURN = gt_return.
    CALL FUNCTION 'RH_UPDATE_DATABASE'
      EXPORTING
        VTASK = 'V'.
    commit work.

You can try to split the update tasks ie Put the 0014 logic inside a custom function module.. make sure to set the 'Update Module' Processing Type in its Attributes. & then call this custom function IN UPDATE TASK fom 9015.
~Suresh

New Infotype Framework

Hello!
I'm just going to implement a new Infotype that should use the Data Sharing functionality for Concurrent Employment. I've read a document about the implementation of the "new" Infotype Framework, but I haven't found an example how to use it for my needs. Is there an example for the use of the Infotype Framework (e.g. Classes CL_HRPA_DATA_SHARING, CL_HRPA_INFOTYPE_FACTORY, ...).
Has anyone ever used the framework to insert/modify an IT-record?
Thanks in advance!

Hi Juergen,
I know i am too late in replying to your question.
However, better to be late than naver, I thought I will share with you how i achieved it in my last project.
You can refrer to the below example code ( Logic for inserting record in infotype 0015).
Note: Structure wa0015 type PA0015 contains the data which you want to
        update in infotype 0015.
FIELD-SYMBOLS: <ls_pnnnn> TYPE p0015.
ASSIGN p0015 TO <ls_pnnnn> .
create instance
CALL METHOD cl_hrpa_masterdata_bl=>get_instance
    IMPORTING
      masterdata_bl = g_masterdata_bl.
CREATE OBJECT g_message_handler.
MOVE-CORRESPONDING wa0015 TO <ls_pnnnn>.
<ls_pnnnn>-infty = 0015.
start trial
    CLEAR g_magic_cookie.
CALL METHOD g_masterdata_bl->start_trial
    IMPORTING
      magic_cookie = g_magic_cookie.
create infotye container
CLEAR g_is_ok.
CALL METHOD g_masterdata_bl->get_infty_container
    EXPORTING
      tclas           = c_tclas
      pskey           = <ls_pnnnn>-pskey
      message_handler = g_message_handler
    IMPORTING
      container       = g_container.
<ls_pnnnn>-pskey     = g_container->a_pskey.
g_container_nnnn ?= g_container.
g_container      ?= g_container_nnnn->modify_primary_record( <ls_pnnnn> ).
insert record in infotype
DATA: ls_bapiret1 TYPE bapiret1.
CLEAR g_is_ok.
CALL METHOD g_masterdata_bl->insert
    EXPORTING
      message_handler = g_message_handler
    IMPORTING
      is_ok           = g_is_ok
    CHANGING
      container       = g_container.
success
IF g_is_ok = c_true.
CALL METHOD g_masterdata_bl->approve_trial
    EXPORTING
      magic_cookie = g_magic_cookie.
commit work
CALL METHOD g_masterdata_bl->flush
    EXPORTING
      no_commit = space.
error
IF g_is_ok IS INITIAL.
discard trial
CALL METHOD g_masterdata_bl->discard_trial
    EXPORTING
      magic_cookie = g_magic_cookie.
append errors
DATA: lt_msg TYPE hrpad_message_tab,
        ls_msg LIKE LINE OF lt_msg,
        ps_return TYPE bapiret1.
IF g_message_handler->has_abend( ) = 'X'.
    CALL METHOD g_message_handler->get_abend_list
      IMPORTING
        messages = lt_msg.
ELSEIF g_message_handler->has_error( ) = 'X'.
    CALL METHOD g_message_handler->get_error_list
      IMPORTING
        messages = lt_msg.
ELSE.
    EXIT.
ENDIF.
LOOP AT lt_msg INTO ls_msg.
    CALL FUNCTION 'BALW_BAPIRETURN_GET1'
      EXPORTING
        type       = ls_msg-msgty
        cl         = ls_msg-msgid
        number     = ls_msg-msgno
        par1       = ls_msg-msgv1
        par2       = ls_msg-msgv2
        par3       = ls_msg-msgv3
        par4       = ls_msg-msgv4
      IMPORTING
        bapireturn = ps_return.
    APPEND ps_return TO pt_return.
ENDLOOP.
ENDIF.
Regards,
Dinesh Pandey

CUP - Issue regarding creation of New SAP ID in CUP.

System : SAP GRC 5.3 SP 12..
We have requirement where in we need to design a workflow for creation of New SAP ID.
The Naming convention followed for SAP ID is FIRST LETTER of FIRST NAME and LAST NAME with maximum 8 characters.
For Eg
JOHN SMITH would have SAP ID as JSMITH
JERRY SMITH would have SAP ID as JSMITH01
The requirement here is when user fill the REQUEST FORM for NEW User ID there is field where in the requestor need to put the desired SAP ID,
Can a validation be set OR Logic be written so that user can put the SAP ID as per the naming convention..?
Also , any other solution as to how the situtation can be handled in CUP...
Regards.
Ajit

Hi Ajit,
Yes, you can maintain the user ID in the Active Directory. User id will be now auto populated in the request form, from Active Directory when we data Source is LDAP -Actice directory. So when user login to end user form to create a request, It's all information( user details + manager details ) will fetched from Active Directory.
It is not possible to change userid in later stage of approval in the request.
You can have security as final stage and guide them to create user manually as per naming convention.
Make auto provisioning OFF in CUP
Kind Regards,
Srinivasan

Creation of new domains in weblogic

Hi All,
I need to create two new domain in weblogic.
It should be start & stop from the admin console.
How to do that. What is node manager?
Just assigning the managed server with machine will do the start and stop from admin console. ?

creation of new domain in weblogic

EA-FIN New Depreciation - How to restrict creation of 'new intervals' ?

Hi Everyone,
We have turned on the EA-FIN Business Function Extension and are wondering if there is a way to restrict the creation of new intervals using company codes. We have three companies in our SAP system and want only one of them to be able to create new intervals. Is there a standard way to do this or only be development? All ideas are welcome!
So far we tried to search if there is an Authority Object, which could be used to apply this restriction with no luck. Could it be done using Validations?
Thanks in advance,
Erne

why would you want this? intervals are just a technical item... so long as the numbers are correct and the calculation is logical to follow, why would you care?
you can probably achieve this by:
1 - immediately blocking every asset record so that no other postings can be made
2 - not allowing any time-dependent changes to occur. this might be possible via authorization or you could remove the time intervals button via a simple screen modification
but I don't understand why this is wanted.

Strategy 82----How to stop creation of New Production Order

Hi All,
My client is facing problem with the material which having Strategy 82- Assembly to Order, As when they make a sales order , w,.r.t that a Production order is made automatically by system,. User complete the production process and deliver this material , now when ever the Sales user change "Credit Block: in that particular sales order again a New production order created to this sales order, How to control his creation of new Production order? As if new production Order create it brakes the link between Sales order and the previous Production order which is already in delivered status.
Your Prompt response will be appreciated.

HI ,
I am closing this thread , as I know how to got a control on trhis, As of behaviour, startegy 82 says every time u change in sales order it will create a new Production order during saving, if the previous order is not been in ONLY REL status. So the only option to control this is in S.O ,change the Item category to "CN" i.e NO MRP when if required there has been any modification to S .O. In std SAP system item catageory has to be congiured , in SPRO SALES we can do the necessary settings.

Creation of new Infotype Important

Similar Messages

Maybe you are looking for