Infotype creation process

hello,
i have got a requirement to create an infotype.. i don't have any idea on that.. can i get a detailed step by step process on how to create an infotype..
thanks in advance

Step 1: Create Infotypes
i.     Goto Transaction PM01 To create Infotypes:
ii.     Enter the Infotype Number and say create all.
iii.     The following message would display:
i.     PSnnnn Does not exist. How do you want to proceed?
iv.     Click
v.     A maintain Structure screen appears.
   Fill in the short text description and the PS structure of the Infotype.
Since the fields Personnel No, Employee Begin Date, End Date, Sequential Number,
Date of Last Change, Name of user who changed the object are available in the PAKEY and PSHD1 structure, define the PSnnnn structure with only the fields you needed.
vi.     Once the PS Structure is created, save and activate the structure.
vii.     In the initial screen of PM01, now click on .
Create a new entry for the infotype.
Fill in the values as mentioned below and save.
          Infotype Characteristics:
Infotype Name of the infotype_ Short Text: __Short Description________
General Attributes :
Time constraint = 1      Record must have no gaps, no overlapping
Check Subtype Obligatory layout of an infotype screen depends on the subtype
Display and Selection:
            Select w/ start   = 3     Valid record for entered data
            Select w/ end    = 5     Records with valid dates within the period entered
Select w/o date = 6     Read all records
                            Screen header   = 02   Header ID
Create w/o end = 1     Default value is 31.12.9999
Technical Data:
Single screen = 2000
        List screen = 3000; List Entry Checked.
viii.     In the initial screen of PM01, now click on .
Choose the infotype entry in the list.
Fill in the values as mentioned below and save.
Technical Attributes:
In    tab section,
The following attribute values are given:
Applicant DB Tab = PAnnnn      Infotype Name
Subtype field         = SUBTY
Subtype table         = T591A
Subty.text tab.        = T591S
Time cnstr.tab.       = T591A
Prim. /Sec.             = I Infotype
Period/key date      = I Interval
and .
ix.     Infotype Screen Modification:
Edit Screen 2000 from PM01 for the Infotype.
ABAP Editor for the Infotype Program MPnnnn00 will be displayed.
Click . Flow Logic will be displayed.
Create two modules: wity your logic to implemented
Message was edited by: MohanVamsi Krishna

Similar Messages

Getting syntax error in "SAPLBBP_PDH_CUF" in shopping cart/RFx/PO creation process in SRM7.0.Is it Patch issue?

Getting syntax error in "SAPLBBP_PDH_CUF" in shopping cart/RFx/PO creation process in SRM7.0.Is it Patch issue?

Hi, something wrong with your customer fields...
Please, check them...

PO Creation Process in Classic Scenario

Hi
I want to understand the exact PO creation process in a classic scenario. Once the buyer clicks on 'Create Purchase Order' in the SOCO, what are the series of steps that are triggered till the PO number gets displayed in the SOCO screen?
I assume that the shopping cart has all required data and ready for PO creation.
With Regards
Sathya

Hi,
The shopping cart is created and approved in SAP Enterprise Buyer. The remainder of the procurement process takes place in the backend ERP system(s) and all other follow-on documents, such the purchase order, goods receipt/service entry sheet and invoice, are located there. With SAP Supplier Self-Services, you have partial supplier involvement for the operational procurement business scenarios when buying materials. There is no support for services.
Shopping Cart
SAP Enterprise Buyer
Approval
SAP Enterprise Buyer
Purchase Order
Backend system
Goods Receipt
Backend system (can be pre-entered in SAP Enterprise Buyer)
Invoice
Backend system (can be pre-entered in SAP Enterprise Buyer)
Please award the points if it helps.
BR,
Vijay Mittal

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Database creation process hangs

I am manually creating a database on Windows 2k3 server using Oracle 11 r2. Using the Database Configuration Assistant to create a database, the process hangs for hours.
I figured out and triedthe following:
1. I have attempted using the GUI tool more than once to create the database and each time it hangs.
2. Using the scripts have been created using the with configuration tool, I manually attemped to create database. -- I have attempted more than once.
3. The database creation process hangs while running the EXECRM.SQL file that is called by the CATPCNFG.SQL which is called by CATPROC.SQL which is called by CreateDBCatalog.sql
3. The EXECRM.SQL file hangs on the following statement EXECUTE DMBS_RMIN.INSTALL;
I'm not sure why the PL/SQL packag is hanging at this point. Any help is appreciated.
Thanks,
Sheila

I was able to create the databases prior to installing Enterprise Manager Grid control. I deleted the databases to re-create so they would be registered with Enterprise manager. Once I install Enterprise manager the creation process hung. I have also installed Essbase and Oracle/Hyperion Enterprise Performance Management Suite on the server. I'm trying to do some research on these BI tools.
I'm tempted to uninstall Essbase and the Hyperion producst along with Enteprise Manager and start from scratch to test to see if I can create a database without these other products.

Pa custom infptype and org management infotype creation

hi experts,
pa custom infptype and org management infotype creation
steps are same or not.
If any difference b/w both plz give me step by step procedure.
Regards,
Sandeep

PA infotype will create in PM01 everything we need fill from PM01.
OM infotype
:- 1. we need to create HRI9XXX structure.
2. PPCJ t-code u can create from this t-code.
PA INFOTYPE CREATION
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)
Edited by: sapabap229 on Aug 30, 2010 11:19 AM

Organization Management/ Personnel Development Infotype Creation

Hi Experts,
Like Personnel Administration Infotype 9xxx,
xxx- series.which are created using PM01 Transaction.
What is the approach to create Organization Management/ Personnel Development Infotype Creation.
Do they have series 9xxxx.
Please advice.
Thanks in Advance.
Regards,
IFF

Hi irfan,
Have u checked this thread?Have a look at the pdf mentioned in the thread.
how to create OM Infotype
Check ur gmail as well.
Regards,
Manoj.

Error - Cube Builder Creation Process

Hi Guys,
I´m working with SSM 7.5 (SP10) under NetWeaver and I´m trying to create a PAS Cube by the Cube Builder Resource.
I´ve already created the CBDEFAULT Manage Model Connection and got sucess in this step.
I created Dimensions and Metrics into Cube Builder Interface and finally I click on "Build PAS Model".
After wait some seconds, I got this massage error:
"There was a problem with the creation of the cube. Check the contents of the cb_build_ITS.trc file in the HOME directory".
Output for the cb_build_ITS.trc file:
LSS>
LSS> set control LINKID SSM_CB_EA
LSS>
LSS> .... capture cube id in a control var to simplify queries on other tables
LSS> access lslink
LSLink> connect SSM_CB_EA
LSLink>
LSLink> SELECT ID FROM CPMS_CB_CUBES WHERE NAME = 'ITS'
[SQL Server Native Client 10.0][SQL Server]Invalid object name 'CPMS_CB_CUBES'.
SQLSTATE: S0002
SQL System code: 208
LSLink> lss create code = 'set control CUBEID ' + ID
LSLink> output proc setcubeid;DB04809 over
LSLink> peek create nohead nonumb
No Fields currently Selected
ACC004:
No Record Has Been Accessed From the Database.
ACC004:
No Record Has Been Accessed From the Database.
CHE FRE
CHE UPD
After look at the script above, I did a little test. I just take the sql statement (SELECT ID FROM CPMS_CB_CUBES WHERE NAME = 'ITS') and runned into my NetWeaver (SQL Server) database, where are stored the CPMS tables.
I got the same error into SQL Database (invalid object name).
For this sql run without problems, I need fix the database and schema name in front of my CPMS table name.
How can I configure/fix this informations into the PAS Creation Script?
Enjoy Answers.
Best Regards,
Bruno Heissler

Bala,
Into PAS, I tried test the Link ID connection and no user id prompt appeared to me. I just got a massage "Connection Sucessed".
So I decided remove the ODBC Connetion related with the Linkd Id in SSM Server and recreated it checking all the steps that are necessary in the SSM Guides.
Now, I can open de PAS, test my SSM_CB_EA Link Id, and look for a prompt asking for User ID and password. The userid, in my case, is SAPCEXDB, that according what you said, is the right information.
So now, I tried create again a Cube in Cube Builder Interface.
After the creation process I got a new error "Pilot Software Application Server Error. Your request encountered an error. ErrorCode: 30".
After got this error, I did a little test. Into the Model Connections Administration step, I checked the CBDEFAULT connection, that is necessary to Cube Builder works.
Follow the parameters:
- Model Connection: CBDEFAULT
- PAS System Name: LOCALHOST
- PAS System Logon:
- Password:
- PAS Model: INITIAL
- PAS User: CBADMIN
- Password:
- INI File: lsserver.ini
- Service: PILOT
Testing this connection I got an error "Error occurred trying to connect; login failed".
All of my Model Connections are working fine (getting success in test connection), including the model connection related to the Cube that I´m trying to create, I means (CBCUBE_MM ; CBCUBE_SC).
I also checked into the Application Server, and there are a list of users. I checked the CBADMIN user, and it´s configured with EXCLUSIVE Default Access Mode for the INITIAL Model Name.
What could be the problem?
Best Regards,
Bruno Heissler

Item creation process

Hello,
Cannot define item attribute values during manual item creation process. Please, help. Maybe I’ve missed some setup?
Application : Advanced Product Catalog
Responsibility : Development Manager
Oracle Applications : 12.1.3
Development Manager > Item Catalog > Create Production Items
Kind Regards, A.

Hello Oliver,
we do not use the CRM quotation. Our quotations are maintained directly in R/3 and connected to the CRM Opportunity via the submission number. This number is written from CRM to R/3 when the Opportunity is saved via a custom RFC enabled Function module. The number is the link for the Tab Quotations in the Opportunities.
I'm currently developing a batch input in wich allows us to provide a button in the CRM Opportunity with the function that a new Quotation is created in R/3 with the submission numer from the Opportunity and the Contact Partner as the sold to party.
Regards
Gregor

LC Rights Management End User can not find groups or users during policy creation process

hello,
I'm using LC8.0.1 turnkey install on win2003 box.
Problem is LC Rights Management End User can not find groups or users (search result is empty) during policy creation process, thus can not apply specific restriction to certain groups or users.
I have create a user in the DefaultDom and assigned the following roles:
Live Cycle Rights Management Invite User
Live Cycle Rights Management End User
How can I allow the above created user to search for groups and user during policy creation? Thanks.

Good catch Phuc. Make sure you do this for each Policy Set as well as My Policies.
Here's an overview of Policy Sets:
http://blogs.adobe.com/security/2008/04/delegating_control_over_policy.html
Cut and paste the URL.

Tables involved transaction BP - Customer creation process.

I need to create a Workflow in transaction BP, but, I don´t know what are tables involved in Customer Creation Process.
Does anybody can help me?
Regards.
Simonny.

hi simmony,
The below are some tables which i know related BP .hope it will be helpful
BUT_FRG0010                    Business Partner: Tax Classification
BUT_FRG0011                    Business Partner: Tax Classification
BUT020                         BP: Addresses
BUT021                         BP: Address usages
BUT051                         BP Relationship: Contact Person Relationsh
BUT052                         BP Relationship: Addresses
BUT053                         BP Relationship: Company Interest
BUT054                         BP Relationship (not used yet)
BUT0BANK                       Business Partner: Bank Data
BUT0BK                         BP: Bank Details
BUT0BKU                        BP: Bank Details Usages
BUT0CC                         BP: Payment Cards
BUT0ID                         BP: ID Numbers
BUT0IS                         BP: Industries
BUT100                         BP: Roles
Thanks and Regards
shanto aloor

PD Infotype creation

hello all,
can anyone guide me on PD infotype creation?
With all neccesary steps or links for the same,
Thanks in advance,
Yashvi

Hi,
This was posted by some one else. I do not remeber the link. The following is the procedure
Enter the transaction code PPCI
Enter a four digit infotype number (9nnn) and an infotype name.
Select Field Infotype
Choose Infotype Create.
Choose Check environment to maintain the required entry in table T777I (Infotypes per object type).
Choose the Entry 'T777I' under the list of 'Table Entries' (This list is produced when you choose 'Check' on the First screen of the Transaction PPCI.
Press the 'Change' button and you will be taken to the 'Maintain Table Views' Transaction (SM30).
Press the Maintain button.
From the list of Infotypes locate the custom infotype created and select the entry for that.
Click on the 'Time Constraint' folder appearing on the left hand corner of the screen.
The screen for Change View Time Constraint would appear.
In the object type field put in: O,P,S whatever is relevant to your requirement.Also add the time constraint.
Save it and double click on the 'Infotypes per object type' folder (on the left hand side again).
Create a new entry here for your infotype and save it.
Regards
Vick

Custom infotype creation issue

Hi Experts,
I have a requirement to create a custom infotype based on certain conditions. But there is a problem while saving data in the infotype. The infotype is populated from another infotype automatically through dynamic actions.
But while saving the data for the first time it happens as per the requirements and data gets saved properly.
But when the data is saved for the second time for the same pernr , the previous data is over written even though the new record starts with a different begin data.Also i have created the infotype with time constraint '1'.
can you please let me know if i am missing anything while creating or is this a logic issue .? all the logic has been coded in the flow logic part of the screen.
also if i dont save the data in the infotype it does not pop up any message like 'data not saved' which usually happens with every infotype. Please clarify me on this as well...
Thanks,
Raj Thilak.

Hi,
Check the logic how it is updating the custom infotype . I think it is nothing to do with creation of custom info type
Regards
Krishna

Issue in radio button group in module pool in infotype creation

Hi,
I have a custom infotype,where there are six radio buttons belonging to same group for different mode of payment.Issue is when user clicks a radiobutton,a subscreen opens .there are six different subscreens when user clicks on each of the six radio buttons.
Requirement is when user clicks one button ,one subscreen opens but the other radio buttons(whcih are eligible to be open) gets disabled .I have tried to handle the issue manually through coding ,but i think the issue is with the radiobutton grouping.
How to make the other radio buttons open for input even when the user has clicked on one button and the subscreen opens corresponding to the screen so that the imemediately ther user clicks on another radio button and get the corresponding subscreen opened for him.Pls advise.

I have written a custom module in PBO section of my custom infotype.There i have written this code:-
LOOP AT SCREEN.
    READ TABLE fp_it_payment_opt_open INTO wa_payment_opt_open WITH KEY scrname = screen-name.
    IF sy-subrc = 0.
      screen-input = c_input_on.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
The internal table it_payment_opt contains all the radio buttons and checkboxes and is populated when the radio buttons and checkboxes are turned input on while modifying the screen depending upon course of my price and personnel subarea.
While calling subscreen area in PBO,the radiobuttons get into a state of input-off automatically.so i have written a z-module after
the module hidden_data .
PROCESS BEFORE OUTPUT.
        general infotype-independent operations
MODULE before_output.
CALL SUBSCREEN subscreen_empl   INCLUDING empl_prog empl_dynnr.
CALL SUBSCREEN subscreen_header INCLUDING header_prog header_dynnr.
        infotype specific operations
MODULE p9300.
CALL SUBSCREEN subscreen_area INCLUDING subscr_prog subscr_dynnr.
MODULE hidden_data.
module z_open_paymnt_optns.
My problem has been solved ,hence am closing the thread.Thanks to all of you.

OLAP Universe creation process questions and proposals

We have created an OLAP universe based on a BW-Query. The automatical creation of the OLAP universe does not produce a satisfying result.
We are working with the latest available releases (BOE XI 3.1 SP2 and SAP Integration KIT SP2, SAP BI 7 EHP1).
We have detected that all dimension objects store the name instead of the key field.
Example:
Customer Dimension Object (L01 Customer) = Customer Name
Customer Key Detail Object (L01 Customer Key) = Customer Number
Customer Name Detail Object (L01 Customer Name) = Customer Name
This is not usable for end user because of the following reasons:
1. The detail objects can not be used for merge dimensions, so it is not possible to merge on the supplier number.
2. If you filter on the dimension object you will only see the text in the list of values (LOV) and it is not possible to edit the list of values in the universe to add the supplier number to the LOV as it is possible in relational universes
3. If the user select the detail object always the dimension object in inserted into the report query
4. The "Business Explorer" general setting "Display" of an InfoObject has no effect on the OLAP universe dimension object. If you change it to key always the text is shown. Even if you change the "ValueDisplay as" in the underlying BW Query to "key" is has no effect.
5. The renaming of the L01 object to blank is not possible. You need to rename to " " and then remove on each object the blank.
So we need to modify manually every universe to change the "detail key object" to a "dimension object" and the "detail name object" to reference the new "dimension object" with the key. This manual process has a huge work effort in time. Is there a better solution or enhancements planned in the next releases?
Additionally there should be an option to disable the automatic creation of each characteristic as a subclass in the universe. A wizard should ask if a subclass should be created or not for each characteristic. Currently there are to many subclasses generated which were mostly not needed.

Hi,
First of all I would say u are lucky to start with SP2. Because whatever modifications you do in Universe those are retained.
We had a big trouble in using BOXIR3.1 FP1.7.
Anyways.. Back to your Questions and My asnwers for those:
1. The detail objects can not be used for merge dimensions, so it is not possible to merge on the supplier number.
Ans: True, Dimension object always shows Short text values by default. but if you can create the logic at SAP BI query level to map short text with keys then your problem will be solved.
2. If you filter on the dimension object you will only see the text in the list of values (LOV) and it is not possible to edit the list of values in the universe to add the supplier number to the LOV as it is possible in relational universes.
Ans: True u cannt edit LOV, but alternate solution to it is create the variable in SAP BI Query, that will appear as prompt in universe which will display the List of values with Key as well as Description.
3. If the user select the detail object always the dimension object in inserted into the report query.
Ans: Logically its correct, because Detail object is always associated with Dimension. Buit if you dont want that dimension in query you can remove that dimension by dragging back.
4. The "Business Explorer" general setting "Display" of an InfoObject has no effect on the OLAP universe dimension object. If you change it to key always the text is shown. Even if you change the "ValueDisplay as" in the underlying BW Query to "key" is has no effect.
Ans: In Query designer even if you ValueDisplay as "Key", but at Object level if there is Text and Key associated for perticulat Infoobject, then so by default the dimension will show the Text and there will be seperate Detail object in universe for Key.
5. The renaming of the L01 object to blank is not possible. You need to rename to " " and then remove on each object the blank.
Ans: Yes this is a big trouble.
Regards,
Nisha

Infotype creation process

Similar Messages

Maybe you are looking for