ABAP Dictionary type FLTP is not allowed for screen element

Hi Experts
I tried to open VBFA in se16 and i got the message in the status bar like this , what does it mean. please explain.
"ABAP Dictionary type FLTP is not allowed for screen element"

Hi,
This is from help
ABAP Dictionary type FLTP is not allowed for screen element
Message no. 37048
Diagnosis
The format of the ABAP Dictionary field is only for use within the ABAP
program and cannot be used in the Screen Painter.
Procedure
The field cannot be used in screens. If you want to output the
information in the field or assign a value to the field from the screen,
you must use an intermediate field with an appropriate format.
Reward points
Regards

Similar Messages

ABAP Dictionory type FLTP is nt allowed for screen Painter!!

Hello All,
ABAP Dictionary type FLTP is nt allowed for screen Painter!! am getting this error message if am giving some input.
Thanks
santu
Edited by: santu4u on Oct 23, 2009 1:48 PM

Hi
Instead of FLTP use Quantity or Currency or Packed Decimals type fields for the Screen Elements.
While you save the data into the database if the database field is of type FLTP the values entered would be automatically converted into FLTP type. We need not take care of this.
---?? What do you mean by IDES version --->
You mean in SE11 or SE16, Wherever it may be you can not use FLTP type on Screen Fields.
This is Standard SAP Procedure, As mentioned Above you can use Packed Decimals or Currency or Quantity Fields
Cheers
Ram
Edited by: Ramchander Krishnamraju on Oct 23, 2009 2:10 PM
Edited by: Ramchander Krishnamraju on Oct 23, 2009 2:13 PM

Set type COMM_PR_UNIT is not allowed for product type

Hello all, I am working in SRM 7.0 and when I try to replicate service master (DNL_CUST_SRVMAS) I have this error:
Set type COMM_PR_UNIT is not allowed for product type
What can I do? I think that is an ABAP problem
Thanks in advance
Rosa Rodríguez

Rosa,
This note is something different and nothing to do with the issue. Can you share how did you resolve the DNL_CUST_SRVMAS issue? We are also getting same error.
Thanks,
Jagadish

FI posting not allowed for WBS Element

Hi All,
While doing down payment billing I'm getting error that FI posting is not allowed for WBS element. But FI periods are open for all months in 2008.
Please suggest how to resolve this issue.
Regards,
Harish

Hello
Account assignment
If you want to post actual costs and commitments to a WBS element, you have to indicate that the WBS element is an account assignment element in the WBS. All objects that can be assigned costs and commitments within a project (for example, orders, networks, or purchase orders) can only be assigned to a WBS element if you have set the account assignment indicator for the element.
In Customizing for the Project System, you can set an indicator to specify that costs are planned for all WBS elements or only for specific WBS elements.
Billing
If you want to post revenues to a WBS element, you have to indicate that the WBS element is a billing element in the WBS.
Reg
assign points if useful

Partitioned IOT of Object Type - mapping table not allowed for bitmap index

Hi,
looks like a feature available for standard Partitioned IOTs is not supported for object based tables, namely the MAPPING TABLE construct to support secondary local bitmap indexes.
Can you confirm behaviour is as expected/documented?
If so, is a fix/enhancement to support mapping table for object-based Partitioned IOTs in the pipeline?
Results for partition-wise load using pipelined table function are very good, look-ups across tens of millions of rows are excellent.
Environment = Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
OS = Oracle Enterprise Linux Server release 5.2 (Carthage) 2.6.18 92.el5 (32-bit)
Here's the potted test-case...
1) First the non object based Partitioned IOT - data is range-partitioned across the alphabet
CREATE TABLE IOT_Table (
textData VARCHAR2(10),
numberData NUMBER(10,0),
CONSTRAINT IOT_Table_PK PRIMARY KEY(textData))
ORGANIZATION INDEX MAPPING TABLE PCTFREE 0 TABLESPACE Firewire
PARTITION BY RANGE (textData)
(PARTITION Text_Part_A VALUES LESS THAN ('B') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_B VALUES LESS THAN ('C') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_C VALUES LESS THAN ('D') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_D VALUES LESS THAN ('E') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_E VALUES LESS THAN ('F') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_F VALUES LESS THAN ('G') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_G VALUES LESS THAN ('H') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_H VALUES LESS THAN ('I') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_I VALUES LESS THAN ('J') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_J VALUES LESS THAN ('K') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_K VALUES LESS THAN ('L') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_L VALUES LESS THAN ('M') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_M VALUES LESS THAN ('N') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_N VALUES LESS THAN ('O') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_O VALUES LESS THAN ('P') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_P VALUES LESS THAN ('Q') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Q VALUES LESS THAN ('R') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_R VALUES LESS THAN ('S') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_S VALUES LESS THAN ('T') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_T VALUES LESS THAN ('U') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_U VALUES LESS THAN ('V') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_V VALUES LESS THAN ('W') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_W VALUES LESS THAN ('X') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_X VALUES LESS THAN ('Y') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Y VALUES LESS THAN ('Z') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Z VALUES LESS THAN (MAXVALUE) PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0))
NOLOGGING PARALLEL -- FLASHBACK ARCHIVE IOT_Flashback_Data
SQL> table IOT_TABLE created.
2) Create the local secondary bitmap index utilising the underlying mapping table
CREATE BITMAP INDEX IOT_Table_BMI1 ON IOT_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
SQL> bitmap index IOT_TABLE_BMI1 created.
3) Quick test to confirm all ok
SQL> INSERT INTO IOT_Table VALUES ('ABC123',100);
SQL> 1 rows inserted.
SQL> SELECT * FROM IOT_Table;
TEXTDATA NUMBERDATA
ABC123     100
4) Now create a minimal object type to use as the template for object table
CREATE TYPE IOT_type AS OBJECT
textData VARCHAR2(10 CHAR),
numberData NUMBER(10,0)
) FINAL
SQL> TYPE IOT_type compiled
5) Attempt to create an object-based range partitioned IOT, including MAPPING TABLE clause as per step (1)
CREATE TABLE IOTObj_Table OF IOT_type (textData PRIMARY KEY)
OBJECT IDENTIFIER IS PRIMARY KEY ORGANIZATION INDEX
MAPPING TABLE -- we'd like to use this feature to enable use of Bitmap Indexes...
PCTFREE 0 TABLESPACE Firewire
PARTITION BY RANGE (textData)
(PARTITION Text_Part_A VALUES LESS THAN ('B') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_B VALUES LESS THAN ('C') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_C VALUES LESS THAN ('D') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_D VALUES LESS THAN ('E') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_E VALUES LESS THAN ('F') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_F VALUES LESS THAN ('G') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_G VALUES LESS THAN ('H') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_H VALUES LESS THAN ('I') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_I VALUES LESS THAN ('J') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_J VALUES LESS THAN ('K') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_K VALUES LESS THAN ('L') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_L VALUES LESS THAN ('M') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_M VALUES LESS THAN ('N') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_N VALUES LESS THAN ('O') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_O VALUES LESS THAN ('P') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_P VALUES LESS THAN ('Q') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Q VALUES LESS THAN ('R') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_R VALUES LESS THAN ('S') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_S VALUES LESS THAN ('T') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_T VALUES LESS THAN ('U') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_U VALUES LESS THAN ('V') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_V VALUES LESS THAN ('W') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_W VALUES LESS THAN ('X') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_X VALUES LESS THAN ('Y') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Y VALUES LESS THAN ('Z') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Z VALUES LESS THAN (MAXVALUE) PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0))
NOLOGGING PARALLEL -- FLASHBACK ARCHIVE IOT_Flashback_Data
This errors out with the following...
SQL Error: ORA-25182: feature not currently available for index-organized tables
25182. 00000 - "feature not currently available for index-organized tables"
*Cause:    An attempt was made to use one or more of the following feature(s) not
currently supported for index-organized tables:
CREATE TABLE with LOB/BFILE/VARRAY columns,
partitioning/PARALLEL/CREATE TABLE AS SELECT options,
ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
*Action:   Do not use the disallowed feature(s) in this release.
6) Re-running the create table statement in step 5 without the MAPPING TABLE clause works fine. Not surprisingly an attempt to create a secondary local bitmap index on this table fails as there's no mapping table, like so...
CREATE BITMAP INDEX IOTObj_Table_BMI1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
CREATE TABLE with LOB/BFILE/VARRAY columns,
partitioning/PARALLEL/CREATE TABLE AS SELECT options,
ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
*Action:   Do not use the disallowed feature(s) in this release.
CREATE BITMAP INDEX IOTObj_Table_BMI1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL
Error at Command Line:99 Column:13
Error report:
SQL Error: ORA-00903: invalid table name
00903. 00000 - "invalid table name"
7) Creating a secondary local b-tree index is fine, like so...
SQL> CREATE INDEX IOTObj_Table_I1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
index IOTOBJ_TABLE_I1 created.
8) A quick test to ensure object table ok...
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DEF456',500));
SQL> 1 rows inserted.
SQL> SELECT * FROM IOTObj_Table;
TEXTDATA NUMBERDATA
DEF456     500

Thanks Dan,
the intention is to range partition based on the initial character, so A* -> Text_Part_A, B* -> Text_Part_B, and so on.
Here's an example, using an empty IOTObj_Table as created previously.
1) Set up & confirm some test data (two 'D's, one 'N', and two 'Z's)
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DEF456',500));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DDD111',510));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('N3000',515));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('ZZ1212',520));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530));
SQL> COMMIT;
SQL> SELECT * FROM IOTObj_Table;
TEXTDATA NUMBERDATA
DDD111     510
DEF456     500
N3000     515
Z111X     530
ZZ1212     520
2) Just to prove our IOT is enforcing the Primary Key based on the TextData attribute, try to insert a duplicate
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530));
Error starting at line 141 in command:
INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530))
Error report:
SQL Error: ORA-00001: unique constraint (OCDataSystems.SYS_IOT_TOP_84235) violated
00001. 00000 - "unique constraint (%s.%s) violated"
*Cause:    An UPDATE or INSERT statement attempted to insert a duplicate key.
For Trusted Oracle configured in DBMS MAC mode, you may see
this message if a duplicate entry exists at a different level.
*Action:   Either remove the unique restriction or do not insert the key.
3) Now confirm that our data has been slotted into the range-based partition we expect using the PARTITION clause of SELECT...
- The two 'D's...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_D);
TEXTDATA NUMBERDATA
DDD111     510
DEF456     500
- The single 'N'...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_N);
TEXTDATA NUMBERDATA
N3000     515
- The two 'Z's...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_Z);
TEXTDATA NUMBERDATA
Z111X     530
ZZ1212     520
4) And to wrap up confirm an empty partition
SELECT * FROM IOTObj_Table PARTITION (Text_Part_W);

Method SAP_WAPI_WORKITEM_COMPLETE not allowed for type F

Hi Gurus
I have created a webdynpro abap application in which these steps
1. Application triggers the workflow and workitem got created through FM1.
2. Workitem loads up webdynpro abap application from portal or outlook by changing settings in SWFVISU transaction.
3. Application completes the workflow by calling FM2.
Here FM1 is SAP_WAPI_START_WORKFLOW which returns the workitem id. When I am giving the same workitem id in function module SAP_WAPI_WORKITEM_COMPLETE , it is giving me error that Method SAP_WAPI_WORKITEM_COMPLETE not allowed for type F
My workflow has only one activity step which is mapped with class CL_PT_REQ_WF_ATTRIBS and method DUMMY. I have checked the synchronous method.
Please let me know how can I correct it.
With regards
Manu Sharma

Hi
You need to give the workitem id of the dialog task which has been configured in SWFVISU. You will get this workitem id via application parameter in your Webdynpro method.
Wokflow will be completed, if all the steps has been executed
Vinoth
Edited by: S Vinoth on Oct 27, 2010 10:08 AM

The operation is not allowed for result set type FORWARD_ONLY

Hi,
I am trying to use scroll insensitive resultset in following manner-
Statement stmt = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
ResultSet rs = stmt.executeQuery("some sql here");
rs.last();
but the rs.last() throws this exception-
com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: The operation is not allowed for result set type FORWARD_ONLY.
     at com.sap.dbtech.jdbc.ResultSetSapDB.assertNotForwardOnly(ResultSetSapDB.java:2725)
     at com.sap.dbtech.jdbc.ResultSetSapDB.last(ResultSetSapDB.java:557)
Database version: Kernel    7.5.0    Build 019-121-082-363
Driver Version: MaxDB JDBC Driver, MySQL MaxDB, 7.6.0    Build 030-000-005-567
This used to work with 7.5 version driver. Why this is failing with 7.6 driver, any clues?
Thanks,
Vinod

Hi Vinod,
due to performance improvement when using forward only cursor we changed the default for the resultset type from TYPE_SCROLL_SENSITIVE to TYPE_FORWARD_ONLY starting with JDBC driver version 7.6. So I guess the exception comes from a statement where you didn't set the resultset type while creating it. Please check if all of the statements that you want to be scrollable have set the correct resultset type.
Regards,
Marco

Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'

Hi All,
I created the wsdl for mobile and I tried to send a SOAP request from Altova XMLSpy. However when I geive the wsdl in 'wsdl file location' I receive the following.
File http://127.0.0.1:8080/B1iXcellerator/exec/dummy/com.sap.b1i.vplatform.scenarios.setup/vPac.sap.B1Mobile/001sap0003_sap.B1Mobile.wsdl is not valid.
Invalid XML schema: 'Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'.'
Error location: wsdl:definitions / wsdl:types / xs:schema / xs:element / @type
Any Idea?
Vangelis

Hi,
it seems that Altove did not cope with defaultNs prefix that is used for marking default namespace.
just look up in your <xs:schema > tag what namespace prefix is used for your namespace - you shall find there something like this
<xs:schema xmlns:ns0="your.namespace.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
and replace prefix defaultNs with prefix of your namespace (in example above it would be ns0)
There might be several usages of defalutNs iside of WSDL (at least in my case were two) so replace it everywhere using same approach
Best regards, Artem

Rebate-Manual payment is not allowed for this agreement type

Hi,
While processing the Rebates, after the Sales cycle till Billing document, when i i try to process the partial settlement it is givin a message as "Manual payment is not allowed for this agreement type"
could you please suggest.
Regards
AS

Hi AS
If you want to do manual payment then in VB)2 select the Agreement type and then in that agreement type check wheather Manual rebate order type has been assigned or not and Manual payment has been checked or not . If they are not maintained and Checked then maintain the rebate document type and check the box Manual accruals and then you can do Manual Payment for that agreement
Regards
Srinath

Activity type E not allowed for equipment entered

Dear Sir , We are using ETM . Following error is coming while creating performace based document .
Activity type E not allowed for equipment entered
Regards
Anil

Give 1 for both type and give it a try.
for target=actual which is type 5 pls check the link below
http://help.sap.com/saphelp_46c/helpdata/EN/66/bc6faa43c211d182b30000e829fbfe/content.htm

Transaction CLM1 not allowed for notification type QL

Hello guys,
one of our user try to open the transaction CLM1/CLM2/CLM3 he getting error message Transaction CLM1 not allowed for notification type QL
please any one give solution for this issue.
find the error screen shot for your reference.
Thanks
Surya

Hello Surya,
Have you done Basic configuration for Claims processing in SAP Project System.
SPRO > Project System > Claim > Notification - Claim > Notification creation
Also check config for Settings for Claims.
Refer sap help for more details
SAP Library - Claim Management
Regards
Tushar

Transaction QM03 not allowed for notification type MQ

HI Dears,
The following error is appearing when i want to view my notification created through defects
Transaction QM03 not allowed for notification type MQ
How to rectify it ?
Alagesan

Hi,
Check IQS3 transaction also....
Cheers,
Tushar

ESS Business Package Error: Period type not allowed for profile ESS

Hi,
We are trying to configure the business package for Employee Self Service on Enterprise Portal 6.0. We followed this SDN contribution <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a">ESS doc guide</a>
So far we have successfully deployed the business packages and followed all the configurations that were pointed out in the doc guide. Unfortunately when we try to access the Employee Self-Service portal pages (Overview, Employee Search, etc), we encounter this error:
Critical Error:
Period type not allowed for profile ESS, error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Period type not allowed for profile ESS, error key: RFC_ERROR_SYSTEM_FAILURE
Any ideas on how to fix this issue?
Regards,
Jojo

Hi Jojo,
Have you solved the problem? If yes can you please help me even I am facing the same error.
this is very help full to me .
Thanks and Regards,
Shilpi.

Error in RFx : Item type 'Service' not allowed for this Item

hi , experts,
We use SRM7.0 in Standalone scenario .
i get an error when i transfer SC to RFx :     Line 0001: Item type 'Service' not allowed for this Item .
if someone kindly tell me how to correct this Error.
another question is ,in the Standalone scenario , can we create Service Master with multiple level(hierarchy) use Tcode 'COMMPR01 ' ?
   reagrds
           claud

Hi Claud,
SRM does not support hierarchy in service for operational documents like PO, contract, confirmation and invoice in SRM 7. It does support hierarchy in service only for RFx doucments. You need to activate the hierarchy template for SRM for that.
Thanks and regards,
Ranjan

Error : Wage Type is not allowed for personnel SG grouping for WT 3

Hi All,
When i am trying to create wage type Degree allowance i am getting error like below.
WT xxxx is not allowed for personnel SG grouping for WT 3 (from 01.09.2006 to
31.12.9999)
     Message no. PG 074
Diagnosis
     In the "Personnel Subgroup Grouping for Primary Wage Types" view
     (V_001P_K), the employee is assigned to personnel SG for primary wage
     types 3. However, this grouping is not valid for wage type xxxx in the
     period from 01.09.2006 to 31.12.9999.
Please let me know where i needs to check.
Thanks.

try to change the start date and try like 01.01.1990 like this
juss chk and update

ABAP Dictionary type FLTP is not allowed for screen element

Similar Messages

Maybe you are looking for