Authorization at data element level

Hi all,
I have a requirement where i have to put a authorization check at data element BANKN .
In all the transactions which use BANKN data element( e.g FK01 , FK02, FK03 etc) , i need to put an auth check for Bank number .
Only those users who are authorized will be able to see the Bank number, other wise the field will be masked by ******* .
I tried with field exit , howerever , it gets triigerrred only at Change (that too not completely satisfying the requirement.)
Please provide me a solutiion for the same.
Also , how to mask a particulat field based on a condition
Thanks
Supriya Murudkar

As I said, most of the time, you should do modification of the standard. In 4.7, you only have SSCR.
I don't know FK* transactions, so I can't tell you if there is a BTE for that.
You should have better mentioned them in the title of your post to get more chance to have an answer, and do not mention "authorization at data element" (people wouldn't read it as it makes no sense in SAP).
By the way, another solution would be to use authorizations at transaction level: authorized people would use FK* transactions where bank field would be displayed, while some other people would use ZFK* transactions where bank field is NOT displayed, using transaction and screen variants

Similar Messages

COnVERSION ROUTINE in data element level

how can we write the CONVERSION ROUTINE in data element level for a field in data dictionary ?.........plz if possible give the EXAMPLE code also?

Hi,
You can refer to any of the standard conversion routines like ALPHA to get an idea. It is used in case of work order (AUFNR).
Regards
Sayee

How to make BI Info obj Data element in-herit source DE documntn?

Say I am in ECC. I go to SE11, give table name MARA and then doubleclick on the dataelement 'MATNR'. Then I click on documentation. I get a popup with Short text " Material Number" and Definition "Alphanumeric key uniquely identifying the material'.
I am interested in the latter information that is 'Definition' - & in general whatever documentation comes up for data element in ECC.CRM.SCM,SRM.
Now I log into SAP BI. I find that under characteristic 0Material, the data element is /BI0/oimaterial. When I double-click this datamaterial and press the documentation button, the system says 'No documentation'.
My Questions:
1. IS there a switch we could turn on in source ECC/SRM/CRM/SRM so that the data element in SAP BI inherits the original source field data element documentation.
{ I am not too convinced of the argument- that in BI we have info objects in ECC we have fields - since I am talking of data element level information- I would tend to think of this as an oversight of the designers or de-prioritization !!}.
2. Could we have an ABAP workaround? That is, in BI we identify the tables that house the mapping between the source and destination data elementsa and take out this information. Then we extract the dataelement documentation by function DOCU_GET (from eCC) and use the mapping info above to link SAP BI data element with source data element documentation.
WHY do I want to punish myself as above? My use case is, we take out SAP BI Table, field, metadata etc and create a model in a modeling tool and physical implementation in a 3rd party DW database as our own canonical, application-agnostic corporate datawarehouse. I would want the source data element documentation to flow to this last system as well as the modeling tool.
Regards
Sasanka

That is, in BI we identify the tables that house the mapping between the source and destination data elementsa and take out this information. Then we extract the dataelement documentation by function DOCU_GET (from eCC) and use the mapping info above to link SAP BI data element with source data element documentation.
1) SAP don't supply this, I would imagine, because R/3 isn't the only possible source of data. I'm currently working on an app that extracts from R/3, an Oracle database and APO. From whence should I take the documentation for my MATERIAL info object? While being able to transfer the documentation of data elements might be very useful for your app, I can't see that generally it would be of interest to clients - I've certainly never heard of such a requirement. So, my opinion at least, it isn't a design flaw.
2) As you've pointed out, you can get the tables that do the mapping, so you know the source data elements, so you can get the documentation. I'm not sure of how to store the documentation, but the obvious candidate for a link between infoobject and dataelement would be master data of an own infoobject. You could wrap DOCU_GET in an RFC (if it isn't RFC enabled), and do a direct call between your 3rd party app and r/3 to get the documentation. For information about the mapping tables, I'd suggest asking that question specifically in one of the BI forums.
matt

Mechanism for Info Object Data elements inherit source documentation?

Say I am in ECC. I go to SE11, give table name MARA and then doubleclick on the dataelement 'MATNR'. Then I click on documentation. I get a popup with Short text " Material Number" and Definition "Alphanumeric key uniquely identifying the material'.
I am interested in the latter information that is 'Definition' - & in general whatever documentation comes up for data element in ECC/CRM/SCM/SRM.
Now I log into SAP BI. I find that under characteristic 0Material, the data element is /BI0/oimaterial. When I double-click this datamaterial and press the documentation button, the system says 'No documentation'.
My Questions:
1. IS there a switch we could turn on in source [ECC/SRM/CRm/SRM] so that the data element in SAP BI inherits the original source field data element documentation.
{ I am not too convinced of the argument- that in BI we have info objects in ECC we have fields - since I am talking of data element level information- I would tend to think of this as an oversight of the designers [or de-prioritization] !!}.
2. Could we have an ABAP workaround? That is, in BI we identify the tables that house the mapping between the source and destination data elementsa and take out this information. Then we extract the dataelement documentation [by function DOCU_GET] and use the mapping info above to link SAP BI data element with source data element documentation.
WHY do I want to punish myself as above? My use case is, we take out SAP BI Table, field, metadata etc and create a model in a modeling tool and physical implementation in a 3rd party DW database as our own canonical, application-agnostic corporate datawarehouse. I would want the source data element documentation to flow to this last system as well as the modeling tool.
Regards
Sasanka

go through this links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9214b1e5-0601-0010-fdb0-ec32d43b06e0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8d7cc990-0201-0010-27a3-d0f74b75a1ee

Field exits - is the exit called wherever the data element is used?

Since field exits are at the data element level - does this mean that the field exit will be executed for any screen that uses it? i only have one screen that I want this exit to be called - do I control that when creating the field exit? Or do you not have any control over that?
Thanks!
Scott

No. Field exit will not be called where ever the data element is used. When you create the field exit, you create it for a perticular field in a screen only. So effectively the exit will be triggered only for that field.
- Guru
Reward points for helpful answers

Procedure for creating transparent table, data element and domain

Hi,
Can anybody let me know the procedure for creating transparent table, data element and domain.
Thanks,
Mahathi

Hi
Database table and its components
A database table is the central data structure of the ABAP/4 data dictionary.
The structure of the objects of application development are mapped in tables on the underlying relational database.
The attributes of these objects correspond to fields of the table.
A table consists of columns (fields) and rows (entries). It has a name and different attributes, such as delivery class and maintenance authorization.
A field has a unique name and attributes; for example it can be a key field.
A table has one or more key fields, called the primary key.
The values of these key fields uniquely identify a table entry.
You must specify a reference table for fields containing a currency (data type CURR) or quantity (data type QUAN). It must contain a field (reference field) with the format for currency keys (data type CUKY) or the format for units (data type UNIT). The field is only assigned to the reference field at program runtime.
The basic objects for defining data in the ABAP Dictionary are tables, data elements and domains. The domain is used for the technical definition of a table field (for example field type and length) and the data element is used for the semantic definition (for example short description).
A domain describes the value range of a field. It is defined by its data type and length. The value range can be limited by specifying fixed values.
A data element describes the meaning of a domain in a certain business context. It contains primarily the field help (F1 documentation) and the field labels in the screen.
A field is not an independent object. It is table-dependent and can only be maintained within a table.
You can enter the data type and number of places directly for a field. No data element is required in this case. Instead the data type and number of places is defined by specifying a direct type.
The data type attributes of a data element can also be defined by specifying a built-in type, where the data type and number of places is entered directly.
Two Level Domain Example
A domain defines a field technically and therefore it may
be used at different business levels.
A data element describes the meaning of a domain in a certain business context.
A domain, however, is used for the technical definition of a table field (for example field type and length).
Therefore, although a take-off airport (data element S_FROMAIRP) would have a different business meaning from an airport where a plane lands (data element S_TOAIRP), they could still have the same domain(here S_AIRPID) because technically we could assign the same number of characters whether the airport is a take-off or a landing airport.
Definitions of Table in Database
In SAP R/3 tables are defined as
A) Transparent tables: All of the fields of a dictionary table correspond to a field in the real database table.
B) Pooled tables: Different tables which are not linked to each other with a common key are combined into a TABLE POOL. Several logical tables thus exist as a single real database table.
C) Cluster tables: Several tables linked by a common key may sometimes be combined by the data dictionary and made to exist on the database schema as a single table.
SAP is evolving R/3 tables in transparent tables.
Elaboration on each of the definitions
A transparent table is automatically created on the database when it is activated in the ABAP Dictionary. At this time the database-independent description of the table in the ABAP Dictionary is translated into the language of the database system used.
The database table has the same name as the table in the ABAP Dictionary. The fields also have the same name in both the database and the ABAP Dictionary. The data types in the ABAP Dictionary are converted to the corresponding data types of the database system.
The order of the fields in the ABAP Dictionary can differ from the order of the fields on the database. This permits you to insert new fields without having to convert the table. When a new field is added, the adjustment is made by changing the database catalog (ALTER TABLE). The new field is added to the database table, whatever the position of the new field in the ABAP Dictionary.
Tables can also reside on the database as Pooled tables or cluster tables
Pooled Tables: Different tables which are not linked to each other with a common key can be combined into a Table Pool. The tables contained within this pool are called Pooled Tables. A table pool is stored in the database a simple table. The table's data sets contain, in separate fields, the actual key for the data set to be stored, the name of the pooled table and the contents of the data set to be stored.
Using this schema, several logical tables are combined into a single real database table. Although the data structure of each set is lost during the write to the table pool, it is restored during the read by the ABAP/4 Data Dictionary. The ABAP/4 Data Dictionary utilizes its meta-data to accomplish this.
Since information must be prepared (defined) within the ABAP/4 Data Dictionary when it is read or written to (or accessed), this process itself defines these as not transparent tables
Cluster Tables: Occasionally, several tables may be linked by a common key. The ABAP/4 Data Dictionary can also combine these tables into a single table. Each data set of the real table within the database contains a key and in a single data field, several data sets of the subsequent table for this key.
As mentioned above, these table types require special data handling, therefore they are not transparent tables.
Technical Settings in Dictionary
The data class logically defines the physical area of the database (for ORACLE the table space) in which your table should be created. If you choose the data class correctly, the table will automatically be created in the appropriate area on the database when it is activated in the ABAP Dictionary.
The most important data classes are master data, transaction data, organizational data and system data.
Master data is data that is rarely modified. An example of master data is the data of an address file, for example the name, address and telephone number.
Transaction data is data that is frequently modified. An example is the material stock of a warehouse, which can change after each purchase order.
Organizational data is data that is defined during customizing when the system is installed and that is rarely modified thereafter. The country keys are an example.
System data is data that the R/3 System itself needs. The program sources are an example.
Further data classes, called customer data classes (USER, USER1), are provided for customers. These should be used for customer developments. Special storage areas must be allocated in the database.
The size category describes the expected storage requirements for the table on the database.
An initial extent is reserved when a table is created on the database. The size of the initial extent is identical for all size categories. If the table needs more space for data at a later time, extents are added. These additional extents have a fixed size that is determined by the size category specified in the ABAP Dictionary.
You can choose a size category from 0 to 4. A fixed extent size, which depends on the database system used, is assigned to each category.
Correctly assigning a size category therefore ensures that you do not create a large number of small extents. It also prevents storage space from being wasted when creating extents that are too large.
Modifications to the entries of a table can be recorded and stored using logging.
To activate logging, the corresponding field must be selected in the technical settings. Logging, however, only will take place if the R/3 System was started with a profile containing parameter 'rec/client'. Only selecting the flag in the ABAP Dictionary is not sufficient to trigger logging.
Parameter 'rec/client' can have the following settings:
rec/client = ALL All clients should be logged.
rec/client = 000[...] Only the specified clients should be logged.
rec/client = OFF Logging is not enabled on this system.
The data modifications are logged independently of the update. The logs can be displayed with the Transaction Table History (SCU3).
Logging creates a 'bottleneck' in the system:
Additional write access for each modification to tables being logged.
This can result in lock situations although the users are accessing different application tables!
Create transparent table
Go to transaction SE11. Enter name of table you want to create (beginning with Y or Z) and click on create pushbutton
Enter the delivery class and the table maintenance criteria
The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems .
The display/maintenance indicator specifies whether it is possible to display/maintain a table/view using the maintenance tools Data Browser (transaction SE16) and table view maintenance (transactions SM30 and SM31).
Enter the name of the table field and the data element. The
System automatically populates the technical details for
existing data elements.
So far as possible it is advisable to use existing data elements which befit the business requirements.
However, we may create data elements if need be. The same is shown in the next slide.
To create a data element simply double click on it.
Alternately create a data element by simply choosing the
data type radio button on SE11 initial screen.
Create data element
The system prompts you to create a new data element.
Choose the Yes pushbutton.
Under the data type tab enter the domain name which
determines the technical characteristics of the field.
Further characteristics tab: Allows you to specify a search help assigned to the data element.
It also allows you to specify a parameter id which helps you populate a field from SAP memory.
Field label: Can be assigned as prefixed text to a screen field referring to the ABAP Dictionary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
Create domain
If the domain does not exist in the data dictionary the
system prompts you to create one.
Give the technical characteristics under the definition
tab. Value range allows you value restriction at domain
level.
Value range tab:
As explained in the section Consistency through input checks one can restrict the possible values for a field at domain level itself by either entering fixed values or by specifying a value table under the tab Value range.
Currency/Quantity fields in a table
A currency or a quantity field must be assigned a reference field from a reference table containing applicable qty unit or currency unit.
Field of the reference table, containing the applicable quantity unit or currency
A field containing currency amounts (data type CURR) must be assigned a reference field including the currency key (data type CUKY).
A field containing quantity specifications (data type QUAN) must be assigned a reference field including the associated quantity unit (data type UNIT).
Create transparent table continue
Maintain the technical settings of the table by clicking on the tab

Error after creating Element level join between two different dataset in11G

Hi Experts,
My report is having data from two different datsets, I created two datasets and joined them with Element Level join. I am getting below error.
"The following tags were not closed: DATA_DS. Error processing resource 'http://localhost:9704/xmlpserver/servlet/xdo'. "
But independent datasets are executing with out any errors.
Please let me know, If any one have inputs to resolve this.
Thanks in advance..

Hi,
Can you please explain the resolution in more details. I'm also having the same issue in BI Publisher report when trying to join two data sets with Element Level Link. I have checked that all my columns have alias names.
Thanks,
Piya.
Edited by: 947289 on Jul 18, 2012 5:56 AM

Error while using '*'in the NTE (EDI 850) Segment where '*' is also used as Data Element

Hi All,
I am facing below mentioned error while using '*'in the NTE (EDI 850) Segment where '*' is also used as Data Element
Error: 1 (Field level error)
SegmentID: NTE
Position in TS: 70
Data Element ID: NTE02
Position in Segment: 2
Data Value:
3: Too many data elements
For Eg: NTE*GEN*My Text *goes here
Here, NTE02 should be My Text *goes here. So, how can I use "*" here without changing anything in the EDI message?
Can it be done?
Thanks.

Sorry, no.
X12 does not support an escape character so whatever is used for delimiters become reserved characters.
If you want to allow '*' in the data, you will have to chooser a different Element delimiter. The receiver should read the from this from the ISA Segment so it's supposed to be dynamic but that's not always the case in practice.

Error When using Element level link in Dataset Joins

Hi All ,
I am joining two data sets using element level link ,I am getting the following Error message
ORA-00972: identifier is too long at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:947) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1283) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1441) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3823) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1671) at oracle.xdo.dataengine.XMLPGEN.processQuery(XMLPGEN.java:1660) at oracle.xdo.dataengine.XMLPGEN.processSQLDataSource(XMLPGEN.java:462) at oracle.xdo.dataengine.XMLPGEN.writeData(XMLPGEN.java:387) at oracle.xdo.dataengine.XMLPGEN.writeGroup(XMLPGEN.java:885) at oracle.xdo.dataengine.XMLPGEN.writeGroup(XMLPGEN.java:906) at oracle.xdo.dataengine.XMLPGEN.processGroup(XMLPGEN.java:846) at oracle.xdo.dataengine.XMLPGEN.processSQLDataSource(XMLPGEN.java:496) at oracle.xdo.dataengine.XMLPGEN.writeData(XMLPGEN.java:387) at oracle.xdo.dataengine.XMLPGEN.writeGroupStructure(XMLPGEN.java:288) at oracle.xdo.dataengine.XMLPGEN.writeXMLDataStructure(XMLPGEN.java:221) at oracle.xdo.dataengine.XMLPGEN.processDataSet(XMLPGEN.java:1575) at oracle.xdo.dataengine.XMLPGEN.processMergedDataSet(XMLPGEN.java:1345) at oracle.xdo.dataengine.DataProcessor.processData(DataProcessor.java:376) at oracle.xdo.servlet.dataengine.DataProcessor.processData(DataProcessor.java:317) at oracle.xdo.servlet.dataengine.DataProcessor.render(DataProcessor.java:671) at oracle.xdo.servlet.ReportModelContextImpl.getReportXMLData(ReportModelContextImpl.java:280) at oracle.xdo.servlet.CoreProcessor.process(CoreProcessor.java:346) at oracle.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:101) at oracle.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:1074) at oracle.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:639) at oracle.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:492) at oracle.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:462) at oracle.xdo.servlet.XDOServlet.doGet(XDOServlet.java:261) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.xdo.servlet.metadata.track.MostRecentFilter.doFilter(MostRecentFilter.java:64) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:125) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.xdo.servlet.init.InitCheckingFilter.doFilter(InitCheckingFilter.java:63) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)</
I used alias names for all the columns not to Exceed characters limit of 30 .When i use group level join ,there is no Error .Please help me on this ,I want to use element level link
Thanks,

I put in the curly brackets so my formula now reads
"Total inquiries for " + {CnAttrCat_1.CnAttrCat_1_Description} + ": " + ToText({@InquiryTypeSubtotal})
Now when I check the formula I get the error message "This field name is not known."
Alec

How to use '*' as data Element in the NTE(Edi 850) Segment

Hi All,
I am facing a field level error while using '*' in EDI 850 (NTE segment). '*' is also used as Data Element.
For Eg: NTE*GEN*My Text *goes here
Here, NTE02 should be My Text *goes here. So, how can I use "*" here without changing anything in the EDI message?
I have asked this question before
http://social.msdn.microsoft.com/Forums/en-US/1668e8d8-ee99-4d79-961b-8d26f3a496f8/error-while-using-in-the-nte-edi-850-segment-where-is-also-used-as-data-element?forum=biztalkediandas2
The answer in the above forum was to ask client modify the EDI message.
Previously, our client was using a different technology (other than BizTalk) which was working fine with this format. So, they are insisting on this format only.
Thanks,

Sorry, the answer is the same.
It doesn't matter what EDI platform either side is using, the '*' in the field content conflicts with the '*' that is the element delimiter. That is invalid EDI, there is no way around that short of writing a custom EDI parser.
It's not clear if you're sending or receiving this message. But again, it's really doesn't matter.
1. Change the Element Delimiter to something other than '*'. < or > are not uncommon.
2. If you are receiving the EDI, create a custom Pipeline Component that "handles" NTE02 either by replacing the '*' with a substitute char or deleting it.
3. If you are receiving, you could add extra elements to NTE to accommodate extra fields (since that's how the parser will see them). Then you can join them again in a Map.

BiizTalk 2013 and EDI Message Invalid character in data element

Hi:
Background: I have a Vendor sending us EDI
856 (Advance Shipping Notice). We are using EDI X12 and BizTalk 2013. In the Parties Agreement we use ISA11 = U-US EDI Community of ASC X12. The vendor is sending 'U' in ISA11.
Error:
At the beginning of EDI Schema import, during EDI audit, we get the following error messages, repeated a few time.
Error: 1 (Field level error)
            SegmentID: LIN
            Position in TS: 18
            Data Element ID: LIN09
            Position in Segment: 9
            Data Value:
            6:
Invalid character in data element
Error: 2 (Field level error)
            SegmentID: PID
            Position in TS: 20
            Data Element ID: PID05
            Position in Segment: 5
            Data Value:
            6:
Invalid character in data element
Root Cause: In all the error cases the data
fields contain “Ü” (U with two dots above it). German character.
Question: What is the best way to deal with
the issue or replace “Ü” (U with two dots above it) characters?
Looking forward to your reply.
Regards, Toraj
Toraj [email protected]

I edited the source file and saved it as UTF-8. It seems, it resolved the issue.
Very cool.
Toraj
Toraj [email protected]
Glad that you have solved this issue by yourself, and thanks for sharing your solution to us.
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Need new description for Data Element based on Company Code.

Hi,
Requirement: The data element AUFNR which has the description "Order Number" needs to have description as "Engagement Number" for a specific company code. All other company codes to retain the description "Order Number".
Example: There are three company codes: AAAA, BBBB and CCCC. The company code CCCC wants the description of data element: AUFNR as "Engagement Number" while AAAA and BBBB wants to retain the standard description: "Order Number".
Pre-Work: Before posting this question, i did search however have not found a solution for this.
In SAP i tried to create an Implicit Enhancement at:
Program: RADBTDDF
Sub Routine: SE_DD04T_ROLLNAME_ROLLNAME
However, as the program is SAP Basis program, i was not successful.
Any hints are appreciated and solution is rewarded.
Thanks for your time.
With Regards,
Goutham.

Dear Matthew,
Thank you for the reply.
I am giving some more details into the requirement.
If a user assigned to company code: CCCC (may not be directly, relationship will be drawn) has logged into the SAP system. If he opens the transaction related to Internal Order, like KO01, KO02, KO03 etc. He should be able to see the description of field: "Order Type" as "Engagement Type".
Similarly in the next screen the field "Order" needs to be displayed as "Engagement Number".
However, for users who belong to company codes: AAAA and BBBB the SAP Standard Descriptions will be shown.
Please let me know if this is possible or any inputs in that direction are highly appreciated.
Let me know if further details are required.
Best Regards,
Goutham.
P.S: As far as i know, Anees Jawad proposal would work if it is required to change the description at the system level.

Updating exist FI document BSEG-ZUONR data element.

Hi there,
We're trying to update ZUONR field on an FI document (BSEG) after it has been posted. I looked for a "change fi document" BAPI and have not been able to do so. Is a BDC for FB02 the only choice for such a requirement or is there a FM suitable for this task?

First, thanks for the replies, second my apologies for not being more specific.
Here is the scenario: I have new custom data element added to MIRO, which is eventually stored in the RBCO table (at the line item level.) Our requirement is have this data element moved into the BSEG-ZUONR field.
I am aware of BTEs and have attemped to do so using the 1120 process, but the problem is I don't have access to the original data as entered in MIRO in the tables available in that BTE. It appears that the RBCO table is not even update until after 1120 process is executed.
Once again, thanks for responses.

How we can show authorization object at infoprovider level

hi all
how we can show authorization object at infoprovider level..
shalini

S_RS_ICUBE:
          Auth objects for working with Infocubes and their sub-objects. For example,
          protecting users who can define the Infocube, applying update rules, and
          looking at the data in the Infocube.
In order to execute any query, u must have access to R_RS_ICUBE and S_RS_COMP. S_RS_COMP is
a powerful object that enables u to make choices on how to secure.

Coldfusion create instance of class from data element when cosuming a webservice

I am calling the following wsdl via cfobject https://services-staging.labcorpsolutions.com/webservice/services/LabcorpOTS/wsdl/LabcorpO TS.wsdl
I am attempting to call the following method registerDonor(java.lang.String, java.lang.String, com.labcorp.ots.ws.data.CreateRegistrationRequest) which references the CreateRegistrationRequest data element.
I haven't been successful in creating an instance of the CreateRegistrationRequest class and setting values of its members, as well as the Phone class which is also a data element.
Any assistance would be greatly appreciated in creating instances of methods located in the targetNamespace="http://data.ws.ots.labcorp.com" of the wsdl.
Thanks

Thanks for the explanation and example. At first, I didn't understand what you were getting at, but after reading "Using Top-Level Containers" and "How to Use Root Panes" java tutorials it made much more sense. Unfortunately, the books I've read up to this point, did not cover those topics at all. The books simply stated that the first step in creating a Swing gui was to extend the JFrame, or JApplet, or etc.
Unfortunately, my original problem persists. I continue to get compile-time errors such as:
TestUserInterface.java:5: cannot find symbol
symbol: class UserInterface
location: class projects.web.TestUserInterface
                      UserInterface ui = new UserInterface(); Anyone know why?
Both the classes are in the same named packaged. Below is my code:
package projects.web;
import java.awt.*;
import javax.swing.*;
public class UserInterface extends JFrame{
     JPanel menuPanel = new JPanel();
     JPanel contentPanel = new JPanel();
     JPanel selectionPanel = new JPanel();
     JButton save = new JButton("Save");
     JButton addFiles = new JButton("Add");
     public UserInterface(){
     super("File Upload");
     setSize(500, 500);
     menuPanel.add(addFiles);
     selectionPanel.add(save);
     setLayout(new BorderLayout());
     add(menuPanel, BorderLayout.NORTH);
     add(contentPanel, BorderLayout.CENTER);
     add(selectionPanel, BorderLayout.SOUTH);
     } // end constructor
} // end UserInterface class
package projects.web;
public class TestUserInterface{
     public static void main(String[] args){
          UserInterface ui = new UserInterface();
} // end TestUserInterface class

Authorization at data element level

Similar Messages

Maybe you are looking for