Qualified Lookup Table in Webdynpro Content Generator

I am trying to build a user interface with the webynpro component generators from the business content deployed on the portal. The problem I face is with qualified lookup tables. From the main table, there is an embedded table which contains the qualified lookup table. I can press the "edit" button to open a pop-up window which shows the details of the qualified link. Unfortunately, on MDM 7.1 SP05, the pop-up window contains a table at the top of the screen that forces the entire window to span the width of the table, which will go on quite far because I have about 20 fields in my qualified lookup table. Below I can enter the values for the individual fields, but it is difficult to use because you have to scroll all the way to the right to select drop down values. Is there a way to remove the summary table from the pop-up window for qualified lookup tables? I havent seen an option in the UI config.

Apparently you can configure the fields that are shown in the pop-up window, but it also limits the fields that are displayed on the iView of the main table.

Similar Messages

Updating a qualifier value of qualified lookup table failed

Hello,
I am trying to update a qualifier value of qualified lookup table.
I have written the method attached to this email.
I am not able to modify a qualifier field, that "Installation instructions DAR Update" field of "Vendor Details" table with this method call. Is there anything I am missing or not doing correctly?
Also, I noticed that in SP6 API documentation, this line in section of ModifyRecordsCommand:
Note: Qualifier values is currently not supported by this command. This command simply ignore qualifier values passed in.
First I have used this method failed. After I saw this, I tried to use ModifyRecordCommand but no success still.
I am copying my method content here. qlv1 and qlv2 is geeting new value after setQualifierFieldValue.
It will be highly appreciated if you can help me.
                boolean isUpdated = false;
          final MdmValue mval = record.getFieldValue(qualFieldID);
          qlv = (QualifiedLookupValue) mval;
          QualifiedLinkValue[] qlinkvals = qlv.getQualifiedLinks();
          for (int j = 0; j < qlinkvals.length; j++) {
               qlinkval = qlinkvals[j];
               qrec = qlinkval.getQualifiedLookupRecord();
               tabId = qrec.getTable();
               qfields = qlinkval.getQualifierFields();
               vdrec = getTSVal(tsVals, qrec);
               for (int k = 0; k < qfields.length; k++) {
                    fieldId = qfields[k];
                    fieldValue = qlinkval.getQualifierValue(fieldId).toString();
                    mstr = mdmHandle.getSchema().getField(tabId, fieldId).getName();
                    fieldName = mstr.get(MDMBase.LANG);
                    if (!(vdrec.containsKey(fieldName)))
                         continue;
                    String curTSVal = fieldValue;
                    String darTSval = vdrec.get(fieldName);
                    // If the dar updated value has different timestamp value,
                    // then it means MDM have changed the value after we sent the
                    // last export to DAR.For this case, we won't change status flag
                    if (!(darTSval.equalsIgnoreCase(curTSVal)))
                         continue;
                    FieldId updateFieldID = tsUpdateFields.get(fieldName);
                    //test
                    FieldId iid = tsUpdateFields.get("Parts Breakdown Timestamp");
                    //test
                    try {
                         MdmValue mvalTrue = MdmValueFactory
                                   .createBooleanValue(true);
                         qlv.setQualifierFieldValue(j, updateFieldID, mvalTrue);
                         //test
                         qlv.setQualifierFieldValue(j, iid, mvalTrue);
                         String qlv1 = qlv.getQualifierFieldValue(j,updateFieldID).toString();
                         String qlv2 = qlv.getQualifierFieldValue(j,iid).toString();
                         QualifiedLinkValue qlv11 = qlv.getQualifiedLinks()[1];
                         logger.info(qlv1":"qlv2);
                         //test
                    } catch (IllegalArgumentException e) {
                         // TODO Auto-generated catch block
                         e.printStackTrace();
                    isUpdated = true;
               if (isUpdated){
                    qlv.setCompleteSet(true);
                    mdmHandle.modifyRecord(record,true);
                    mdmHandle.modifyRecord(qrec,true);
Regards

Apparently you can configure the fields that are shown in the pop-up window, but it also limits the fields that are displayed on the iView of the main table.

Insert a record in Qualified Lookup Table

Hello everyone,
I need code to insert a record in Qualified Lookup Table where the non-qualifier is a record of type Country. Other fields are qualifiers.
I tried using QualifiedLookupValue.createQualifiedLink(). However, this only helps to insert in the qualifier values, how can I insert the non-qualifier (Country) value?
Any idea?
Many thanks in advance,
Baez

Hi guys,
Maybe the answer comes late but i'm recently working on this and the API works for me to create and update qualifier values.
Suppose recordMain is the main record, fldQFT is the qualified lookup field in main table, fldQualifier is the qualifier field in QFT table.
To add qualifier value you can use:
QualifiedLookupValue qualifiedLookupValue = new QualifiedLookupValue();
int index = qualifiedLookupValue.createQualifiedLink(recordMain.getId());
qualifiedLookupValue.setQualifierFieldValue(index, fldQualifier, MdmValue);
recordMain.setFieldValue(fldQFT, qualifiedLookupValue);
To update qualifier value, use:
QualifiedLookupValue qualifiedLookupValue = (QualifiedLookupValue) recordMain.getFieldValue(fldQFT);
qualifiedLookupValue.setQualifierFieldValue(index, fldQualifier, MdmValue);
recordMain.setFieldValue(fldQFT, qualifiedLookupValue);
Regards,
James

Qualified lookup table

Hi Guys,
Can you tell me the steps to be followed for importing and syndicating qualified lookup table .
Thanks,
MS Reddy

Hi,
1. Import all the lookup tables used in Qualified table.
2. Import qualified table data along with main table data only. For more than one qualified table record you should have repeated main table record.
E.g.
Qualified Table - Price Information
Lower Bound
Purchasing Info Record ID
Purchasing Organization
Amount
Currency
First three fields are the non-qualifiers amongst which Purchasing Organization is the lookup field. So you need to first populate this field.
Now your main table record is
Supplier     Supplier Part Number     Short Description     Product ID     Service Item     Lower Bound Purchasing Info Record ID     Purchasing Organization     Currency     Amount
AGENCY01          1000               metal processing     IBG-100               False     1     5300000018     Mumbai Purchase Org     Indian Rupee     100.00
1. Map all the main table fields
2. Identify the Display fields of your Qualified table, if your qualified table has more than one Display field then map the fields with the fields marked as D in destination structure e.g. in above given table all the three non-qualifiers are the display fields then mark Lower Bound with the D   Lower Bound field, similarly map the other display fields
3. Select all the Display fields at source side, right click and select Create Compound field. This will combine your input fields and automatically map them with Qualified field.
4. Map the qualifiers
5. Select the unique fields in Matching fields tab and execute the import.
When you syndicate data containing qualified links, it will create the number of output records depending on the number of qualified links.
Regards,
Jitesh Talreja

When to use qualified lookup table?

Hi all,
I am confused with the qualified lookup table and lookup table, for the situation that a company has more than one contact person, I created a table "contact person", which has following fields: first name, last name, phone number, email address.
Questions:
1. should I set "contact person" as a lookup table or qualified lookup table?
2. if to be set as qualified lookup table, which field should be qualifier field? what is the difference between qualifier field and non-qualifier field?
your reply will be very appreciable
Bin

At times data is stored in such a way that duplication is unavoidable due to the storing mechanism and other factors. It may also happen that the data is sparse. The efficient way of storing data in such scenarios is the use of Qualified tables as it reduces the size of the main table and removes the unnecessarily created duplicates.
Check the foll links
/people/pooja.khandelwal2/blog/2006/03/29/taming-the-animal--qualified-tables
/people/avi.rokach/blog/2006/11/14/using-mdm-55-for-data-quality-analysis
MDM data modelling guide
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d4211fa-0301-0010-9fb1-ef1fd91719b6
How to import Qualified tables.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/abe914fa-0301-0010-7bb1-d25c2a4bb655
Also this one.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/792f57b7-0a01-0010-f3b6-881269136a83
Please reward for the same.

Searching for Duplicates records in Qualified Lookup tables

Hi SDNers,
I would like to know,
How to find out how many records having duplicate records in Qualified Look Tables.
In Free form search or Drill down Serach.. I am select the particular Qualified Look up Table. After how can I find Duplicated reocrds.
Any Solution?
Thanks
Ravi

Hi,
If you want to find the duplicates present in qualified table then, you can go to qualified table in data manager and get to know the duplicates....else if you want to find the duplicate links to a record in main table, then you can write an expression in free form search to get the value of duplicate links. but that would be specific to a link value only..e.g. Country is your no qualifier, then in free form search, you can write an expression to get how many links are for USA.
Hope this clarifies your doubt...if not, please elaborate on the requirement.
Regards,
Arafat.

Error in Import to Qualified lookup table

A qualified look up table has 1 Non qualifier and 8 qualifiers.Non qualifier values are X and Y.Records were imported from excel sheet to QLT.
In the first trial, for a NQ 'X' all the qualified values of Y have got imported and vice versa .
Now, I need to replace , Value X with Y in non qualifier and retain all Qualifier values. While doing this, a new record is getting appended in the QLT with NQ 'Y'.
How can record appending in QLT be avoided by replacing only Non Qualifier values?
Need very quick help on this please.
Regards,
Vinay M.S

Hi Vinay,
Set the qualified update to Replace for the non qualifier in the destination fields in Map Fields/
Values pane.
Best Regards,
Silpa Chillakuru

Inserting a record in qualified looup table

Hi All,
I am using MDM 5.5 SP6. I have table structure like this.
Table name:
Representative (main table)
Fields:
     Name          Text
     Age          Integer
     Voter ID     Text
     Gender          Lookup[flat]
     PostandLocation Lookup[Qualified](Multi-valued) --> It refers qualified table 'Post_and_Location'.
Post_and_Location (Qualified table)
Fields:
     Position     Lookup[flat]
     Location     Lookup[Hierarchy](multi-valued) --> It refers hierarchy table 'Locations'
Locations (Hierarchy table)
Fields:
     State          Lookup[flat]
     District     Lookup[flat]
     City          Text
Here, I need add representative details in main table 'representative' using Java API. In webdynpro UI, I will give Name, age,voterid,gender,position, city,district, state.
Here I am struggling that how to lookup hieararchy table value in qualified lookup table(Post_and_Location). How can I achieve this?.Please help me.
I am more happy to give more information regarding this, if anybody needs.
Thanks,
Venkatesh

Hi Bharti,
Thanks for your quick reply. Here I need more explanation on, how to lookup hierarchy table(Location) record in Qualified lookup table (Post_and_Location) using java API. I need more explanation in Java API regarding this.
Because, As per our scenario, Qualified table(Post_and_Location) have a field called 'Location'(type Lookup[Hierarchy](multi-valued)). It looks up Hieararchy table(Locations).
Here, while adding new representative in main table(representative), I need to lookup qualified table(Post_and_Location) record for the field 'PostandLocation' in main table(representative). And also, I need to lookup hierarchy table(Location) record for the field 'Location' in Qualified table.
If you get confuse, please check my table structure above in this thread. If you need more info, I will provide. Please help me to achive this.
Thanks,
Venkatesh

Values of Non-Qualifiers (lookups) not auto-converting.

We've been trying to use Import Server to automatically import records (XML) that had data for qualified lookup tables. Apparently there is an issue with namespaces in both the schema that we mapped to and the source field.
After removing the namespaces, we now have an issue with the non-qualifier that uses a lookup table not automapping it's values and thus retaining the compound field at the Customer main level.
First, the Partner Function is mapped to the Partner Function flat lookup table. At this level, the value auto-converts and the green dot is visible to the left.
Second, at the Customer Partner qualified lookup, the Partner Function is again mapped to the Partner Function lookup. This time, however, the values do not automatically convert and the "AUTOMAP" button must be manually pushed for them to map. The other non-qualifiers (CustomerID, PartnerNum, PartnerSAP_ID) are also mapped and their values auto-convert (green dot).
Finally, at the Customer main level, all of the non-qualified field from the Customer Partner table are mapped and all auto-convert except for the Partner Function field. This requires us to manually push "Automap". Then, and only then, does it allow us to right click on one of the fields and create the compound field to map to the Customer Partner field. Again, the value mapping is not automatic but must be done manually.
This map is then saved and ImpMgr closed. When the IM is reopened with the same map, the compound field is not recreated due to the fact that the Partner Function values did not convert. Once these are redone manually, then and only then can the compound field be recreated and value mapped.
When this same map is used in the Import Server, the error is that the qualified fields cannot be mapped. This brings us back to the lookup fields not value mapping. Likewise, if this same file is opened in Import Manager mannually, and the map applied, it STILL does not convert the values and the Compound Field for the Qualified L/Up table is dropped.
We are using MDM 5.5 SP4 Patch 3.

Hello Christiane,
Yes, this is a very important point and I should have noted it in my original post. Yes, my Default Batch Handling settings are:
Yes - Automap unmapped values
Add - Unmapped Value Handling
Plus:
Replace - Default multi-valued update
Append - Deault qualified update
None - Default matching qualifiers
Also, in my mdis.ini file, my settings are:
Automap Unmapped Value = True
Unmapped Value Handling = Add
Always Use Unmapped Value Handling = True
It used to work when we were in SP4, Patch 2, but have since upgraded to Patch 3, Hotfix 2(?) and can't get it to work.
Thanks for helping!
Don

Qulified lookup table field can be viewed at Maintable.

We have 2 non qualifiers in Qualified lookup table and the field type are lookup flat, If i change the data in this fields, i can able to see the change tracking history at main table level.
Thanks
NK

Hi Krish,
Thats how change tracker in MDM works...
regards
Sowseel

Syndiacting Qualified lookup in new XML

Hi Gurus,
Requiremnet is to syndicate qualified look up data into different XML
.to be specific ..We have created Vendor specific data as Qualified lookup table and are mapping this table in Syndication to INFREC idoc.
But while syndicating it back..the XML file just pulls out the vendor name .Requiremnent was that the XML should pull out MAterial -Vendor specific data.
Questions:
1Is this possible?
2.If yes please help me with this regards..I think i might be missing some setting..
Regards,
Vikrant M Kelkar

Hi Vikrant,
As per my understanding of your requirement you wnat to syndicate the qualified table data in the form of XML.
If this is the case then it is possible.
- In the syndicator the source structure is your repository structure and your destination structure should be an XML schema containing the idoc structure.
- You need to map your qualified table fileds with the corresponding idoc fields.
- If you do not intend to syndicate any other fields you need not map them.
Note:
You need to note the following things while performing Qualifier syndication
1) While syndicating qualified table fields you need to map the lookup field to the corresponding segment.Else it will not allow you to map the fields inside the qualified table
2) You need to make that particular segemnt as Repeatable XML node in the map properties.
3) Once these settings are done you can map the qualified field syou want and they will be syndicated in the form of .XML
4) Also note to map the Root node.At the beginning of the structure.
Hope it helped
Kindly reward points if found useful
Thanks
Simona

Syndicating Selected Qualified Lookup Entries

Hello all!
Here is an issue we are working on. We would like to syndicate entries from a qualified lookup table for a particular customer, but only those where a certain qualifier has a specific value. For example:
Qual Table:
Non-Qual1; Non-Qual2; Qualifier.
Entries:
"AA", "123", "Yes"
"BB", "123", "No"
"CC", "456", "Yes"
So, when I syndicate this customer record, I would only like to syndicate those entries where the Qualifer = "Yes".
"Supress Unchanged Records" only works on the whole customer record and if the Search Criteria is set for "Qualifer = "YES", then it chooses the record (correctly), but syndicates all entries from the table.
Thanks in advance!
Don

Try using
<b>Filter Qualified Links</b> in the <b>Map Properties</b> of the Syndicator.
If activated, syndication results contain only the data selected in the Selection Pane.
Tick the check box under the Value Column for that property. By default that check box is not selected. You have to check it.
This works similar to the 'Filter' check box of the MDM Data Manger.
Limitation as of SP04
- One Global setting per map for qualified links plus one global setting per map for multi-valued lookups.

Accessing lookup table from XSL stylesheet

HI Gentlemen,
Given two XMLTYPE tables: a Master and a Lookup. The Lookup table consists merely of {key, value} pairs. I am about to display Master table contents--subtrees selected from one big XMLTYPE column. The display process is governed by an appropriate XSL stylesheet. Master table elements have data only in their attributes. For example: <time U="2"/> which means that the value of the Unit attribute is 2, meaning "Minute" according to the Lookup table.
My question is: Does anybody of you know a fast and safe method to SELECT from the Master AND Lookup (inner join, as in a pure relational environment), thereby REPLACING the key value with its MEANING (textual interpretation). This would be extremely important as numeric codes do not have meaning to the user. User-friendly behavior requires that all important information be displayed at once. (Note that I have nothing against modifying my stylesheet to query the Lookup table as well, if no straightforward master-detail querying technique exists.)
Please give me an idea if you have.
Thank you in advance, kind regards:
Miklos HERBOLY

HI odie,
Here is the stuff you requested. I admit, it is fairly abundant, but you will see the structure and the main points. Some of the elements are multiple-occurrence, hence the XMLTABLE() solution was no good because of the large number of generated rows. The stylesheet would be ideal to display embedded "nested collections".
Please let me know if you have anything for me.
Thanks, regards
Miklos
HERE ARE THE XMLTYPE MASTER TABLE CONTENTS. TABLE IS NON-SCHEMA-BASED.
=====================================================================
SQL> select * from z;
XML_DOCUMENT
<?xml version="1.0" encoding="WINDOWS-1252"?>
<?xml-stylesheet type="text/xsl" href="file://c:/XSL/ziffer.xsl"?>
<ehd:ehd xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:ehd/go/001" xmlns:ehd="urn:ehd/001" ehd_versio
n="1.20">
<ehd:header>
<ehd:id EX="E7F454A3-0F6E-460e-A495-BBBBBBBBBBB3" RT="1.2.276.0.76.3.1.1"/>
<ehd:version_nbr V="1"/>
<ehd:document_type_cd V="851"/>
<ehd:service_tmr V="2006-07-01..2007-12-31"/>
<ehd:origination_dttm V="2006-05-03"/>
<ehd:provider>
<ehd:provider.type_cd V="KV" S="1.2.276.0.76.5.104" SV="1.0"/>
<ehd:person>
<ehd:id EX="3223" RT="2.3.5.3.T.e.s.t" RTV="1.10"/>
<ehd:person_name>
<ehd:nm>
<ehd:GIV V="Hans"/>
<ehd:PFX V="von"/>
<ehd:FAM V="Mustermann"/>
</ehd:nm>
</ehd:person_name>
<ehd:organization.nm V="KV Hessen"/>
<ehd:addr>
<ehd:STR V="Ottostr."/>
<ehd:HNR V="12"/>
<ehd:ZIP V="50859"/>
<ehd:CTY V="Köln"/>
</ehd:addr>
<ehd:telecom V="tel:030-4005-2121 begin_of_the_skype_highlighting 030-4005-2121 end_of_the_skype_highlighting begin_of_the_skype_highlighting 030-4005-2121 end_of_the_skype_highlighting"/>
</ehd:person>
<ehd:organization>
<ehd:id EX="46" RT="1.2.276.0.76.5.233"/>
</ehd:organization>
</ehd:provider>
<ehd:interface>
<ehd:id EX="SDEBM" RT="1.2.276.0.76.5.109" RTV="1.0"/>
<ehd:interface.nm V="Gebührenordnungsstammdatei / Satzart 851"/>
<ehd:version V="01.30"/>
</ehd:interface>
</ehd:header>
<ehd:body>
<gnr_liste>
<gnr V="01700V" USE="46" USE-DOMAIN="1.2.276.0.76.5.233" VT="2006-05-03">
<allgemein>
<gueltigkeit>
<service_tmr V="2006-07-01.."/>
<effective_tmr V="2006-07-01.."/>
</gueltigkeit>
<legende>
<kap_bez V="1.7" DN="Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregelun
g und Schwangerschaftsabbruch (vormals Sonstige Hilfen)">
<bereich V="II" DN="Arztgruppenübergreifende allgemeine Leistungen"/>
<kapitel V="1" DN="Allgemeine Leistungen"/>
<abschnitt V="7" DN="Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregel
ung und Schwangerschaftsabbruch (vormals Sonstige Hilfen)"/>
</kap_bez>
<kurztext V="Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a."/>
<langtext V="Grundpauschale für Fachärzte für Laboratoriumsmedizin, Mikrobiologie und Infektionsepidemiologi
e, Transfusionsmedizin und ermächtigte Fachwissenschaftler der Medizin für die Erbringung von Laborleistungen gemäß den
Richtlinien des Gemeinsamen Bundesausschusses über die ärztliche Betreuung während der Schwangerschaft und nach der En
tb indung (Mutterschafts-Richtlinien) und/oder der Richtlinien des Gemeinsamen Bundesausschusses zur Empfängnisregelung
und zum Schwangerschaftsabbruch bei Probeneinsendung, "/>
<quittungstext V="Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a."/>
</legende>
<anmerkungen_liste>
<anmerkung V="Die Leistung nach der Nr. 01100 ist nicht berechnungsfähig, wenn Sprechstunden vor 07:00 Uhr o
der nach 19:00 Uhr stattfinden oder Patienten zu diesen Zeiten bestellt werden."/>
<anmerkung V="Im Rahmen der unvorhergesehenen Inanspruchnahme des Vertragsarztes ist die Leistung nach der N
r. 01100 auch dann nur einmal berechnungsfähig, wenn es sich um eine Gruppenbehandlung handelt."/>
<anmerkung V="Die Leistung nach der Nr. 01100 ist ausschließlich bei kurativer Behandlung berechnungsfähig."
/>
</anmerkungen_liste>
<leistungsinhalt>
<komplex V="OBLIGAT">
<leistung V="Persönlicher Arzt-Patienten-Kontakt im organisierten Not(fall)dienst"/>
</komplex>
<komplex V="FAKULTATIV">
<leistung V="Beratung und Behandlung bis zu 10 Minuten Dauer,"/>
<leistung V="2...Beratung und Behandlung bis zu 10 Minuten Dauer,"/>
<leistung V="3...Beratung und Behandlung bis zu 10 Minuten Dauer,"/>
</komplex>
<komplex V="FAKULTATIV">
<leistung V="In Anhang 1 aufgeführte Leistungen,"/>
</komplex>
</leistungsinhalt>
<bewertung_liste>
<bewertung V="5595" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="1" S="1.2.276.0.76.5.234" SV="1.02"/>
<leistung_typ V="GL"/>
</bewertung>
<bewertung V="2797.5" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="2" S="1.2.276.0.76.5.234" SV="1.02"/>
<leistung_typ V="GL"/>
</bewertung>
</bewertung_liste>
<zeitbedarf_liste>
<zeit V="21" U="2" U-DOMAIN="1.2.276.0.76.5.238">
<leistung_typ V="AL"/>
</zeit>
</zeitbedarf_liste>
<pruefzeit V="1" U="2" U-DOMAIN="1.2.276.0.76.5.238">
<zeitprofilart V="3" S="1.2.276.0.76.5.228" SV="1.00"/>
</pruefzeit>
<rlv V="0" S="1.2.276.0.76.5.241" SV="1.00"/>
<leistungsgruppe V="10" S="1.2.276.0.76.5.227" SV="1.00"/>
</allgemein>
<bedingung>
<fachgruppe_liste V="true">
<versorgungsbereich V="2" S="1.2.276.0.76.5.237" SV="1.01">
<fachgruppe V="110" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="111" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="112" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="303" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="357" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="501" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="532" S="1.2.276.0.76.5.114" SV="1.00"/>
</versorgungsbereich>
</fachgruppe_liste>
<anzahlbedingung_liste>
<bezugsraum V="1" U="7" U-DOMAIN="1.2.276.0.76.5.226">
<anzahl V="1"/>
</bezugsraum>
</anzahlbedingung_liste>
<abr_best V="je Behandlungsfall mit Auftragsleistung(en) der Abschnitte 1.7.4 und/oder 1.7.5"/>
</bedingung>
<regel>
<ausschluss_liste>
<bezugsraum V="1" U="7" U-DOMAIN="1.2.276.0.76.5.226">
<gnr_liste V="false">
<gnr V="12220" DN="Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a."/>
<gnr V="12225" DN="Grundpauschale für Vertragsärzte aus nicht in der Nr. 12220 aufgeführten Arztgruppen
bei Probeneinsendung"/>
</gnr_liste>
</bezugsraum>
</ausschluss_liste>
</regel>
<kv V="46" S="1.2.276.0.76.5.233" SV="1.01">
<kennzeichen>
<arztpraxis V="1"/>
</kennzeichen>
<kv_bewertung_liste>
<kv_bewertung V="100" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="2" S="1.2.276.0.76.5.234" SV="1.02"/>
</kv_bewertung>
<kv_bewertung V="150" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="1" S="1.2.276.0.76.5.234" SV="1.02"/>
</kv_bewertung>
</kv_bewertung_liste>
</kv>
<vdx>
<gkv_kontenart_liste>
<gkv_kontenart V="530" S="1.2.276.0.76.5.258"/>
<gkv_kontenart V="463" S="1.2.276.0.76.5.258"/>
</gkv_kontenart_liste>
</vdx>
</gnr>
</gnr_liste>
</ehd:body>
</ehd:ehd>
1 Zeile wurde ausgewählt.
SQL> spool off
==========================
HERE IS THE XQUERY COMMAND
==========================
<?xml version="1.0" encoding='windows-1252'?>

<page xmlns:xsql="urn:oracle-xsql" connection="gksconnection">
<xsql:query xmlns:xsql="urn:oracle-xsql">
SELECT XMLQuery('xquery version "1.0";
declare namespace n1="urn:ehd/001";
declare namespace n2="urn:ehd/go/001";
let $i := /n1:ehd/n1:body/n2:gnr_liste/n2:gnr
where $i[@n2:V = "01700V"]
return $i'
PASSING xml_document
RETURNING CONTENT)
FROM z
</xsql:query>
</page>
======================
HERE IS THE STYLESHEET - relevant part only
======================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:ehd="urn:ehd/001" xmlns:pe="urn:ehd/go/001">
<xsl:output method="html"/>
<xsl:template match="pe:gnr">
<html>
<head>
<title>EBM Ziffer</title>
<style type="text/css">
table
border-collapse:collapse;
table, td, th
border:1px solid black;
</style>
</head>
<body style="font-family:verdana;color:black">
<h2><xsl:text>Ziffer: </xsl:text>
<xsl:value-of select="@V"/>
</h2>
<table border="1">
<tr>
<td><xsl:text>KV</xsl:text></td>
<td><xsl:value-of select="@USE"/></td>
</tr>
<tr>
<td><xsl:text>Gültigkeit</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:gueltigkeit/pe:service_tmr/@V"/></td>
</tr>
<tr>
<td><xsl:text>Bezeichnung Kapitel</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/@V"/>
<xsl:text> </xsl:text>
<xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Bereich</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:bereich/@V"/>
<xsl:text> </xsl:text>
<xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:bereich/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Kapitel</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:kapitel/@V"/>
<xsl:text> </xsl:text>
<xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:kapitel/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Abschnitt</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:abschnitt/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Unterabschnitt</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:uabschnitt/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Block</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:block/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Kurztext</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kurztext/@V"/></td>
</tr>
<tr>
<td><xsl:text>Langtext</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:langtext/@V"/></td>
</tr>
<tr>
<td><xsl:text>Langtext (Fortsetzung)</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:langtext_continued/@V"/></td>
</tr>
<tr>
<td><xsl:text>Quittungstext</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:quittungstext/@V"/></td>
</tr>
</table>

<h4><xsl:text>Anmerkungen</xsl:text></h4>
<table border="1">
<xsl:for-each select="pe:allgemein/pe:anmerkungen_liste/pe:anmerkung">
<tr>
<td><xsl:value-of select="@V"/></td>
</tr>
</xsl:for-each>
</table>

<h4><xsl:text>Leistungsinhalt</xsl:text></h4>
<table border="1" >
<tr>
<th><xsl:text>Komplex</xsl:text></th>
<th><xsl:text>Leistung</xsl:text></th>
</tr>
<xsl:for-each select="pe:allgemein/pe:leistungsinhalt/pe:komplex">
<tr>
<td><xsl:value-of select="@V"/></td>
<td>
<xsl:for-each select="pe:leistung">
<xsl:value-of select="@V"/>
</xsl:for-each>
</td>
</tr>
</xsl:for-each>
</table>

<h4><xsl:text>Bewertungen</xsl:text></h4>
<table border="1">
<tr>
<th><xsl:text>Bewertung</xsl:text></th>
<th><xsl:text>Einheit</xsl:text></th>
<th><xsl:text>Gebührenordnung</xsl:text></th>
<th><xsl:text>Leistungserbringerart</xsl:text></th>
<th><xsl:text>Leistungstyp</xsl:text></th>
<th><xsl:text>Versorgungsgebiet</xsl:text></th>
</tr>
<xsl:for-each select="pe:allgemein/pe:bewertung_liste/pe:bewertung">
<tr>
<td><xsl:value-of select="@V"/></td>
<td><xsl:value-of select="@U"/></td>
<td><xsl:value-of select="pe:gebuehrenordnung/@V"/></td>
<td><xsl:value-of select="pe:leistungserbringerart/@V"/></td>
<td><xsl:value-of select="pe:leistung_typ/@V"/></td>
<td><xsl:value-of select="pe:versorgungsgebiet/@V"/></td>
</tr>
</xsl:for-each>
</table>

<h4><xsl:text>Zeitbedarfliste</xsl:text></h4>
<table border="1">
<tr>
<th><xsl:text>Zeit</xsl:text></th>
<th><xsl:text>Einheit</xsl:text></th>
<th><xsl:text>Leistungstyp</xsl:text></th>
</tr>
<xsl:for-each select="pe:allgemein/pe:zeitbedarf_liste/pe:zeit">
<tr>
<td><xsl:value-of select="@V"/></td>
<td><xsl:value-of select="@U"/></td>
<td><xsl:value-of select="pe:leistung_typ/@V"/></td>
</tr>
</xsl:for-each>
</table>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
=====================================
THE REQUESTED SAMPLE LOOKUP TABLE FOR TIME UNITS
=====================================
<keytabs>
−
<keytab S="1.2.276.0.76.5.238" SN="S_KBV_ZEITEINHEIT" SV="1.00">
<key V="1" DN="Sekunde" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="2" DN="Minute" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="3" DN="Stunde" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="4" DN="Tag" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="5" DN="Woche" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="6" DN="Monat" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="7" DN="Quartal" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="8" DN="Jahr" S="1.2.276.0.76.5.238" SV="1.00"/>
</keytab>
</keytabs>
==================================================================================================
And this is, from an earlier trial with XMLTABLE() what I become when stylesheet is commented out. Only for your information here!
Due to the three "Anmerkung" three rows were generated. What is this notation? I got it when
executing the XSQL sheet without stylesheet. Produced by the browser.
I can not find any info in the whole web.
==================================================================================================

<page>
<ROWSET>
<ROW num="1">
<ZIFFER>01700V</ZIFFER>
<GUELTIGKEIT>2006-07-01..</GUELTIGKEIT>
<KAP_NR>1.7</KAP_NR>
<KAP_BEZ>
Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregelun g und Schwangerschaftsabbruch (vormals Sonstige Hilfen)
</KAP_BEZ>
<BEREICH_NR>II</BEREICH_NR>
<BEREICH>Arztgruppenübergreifende allgemeine Leistungen</BEREICH>
<KAPITEL_NR>1</KAPITEL_NR>
<KAPITEL>Allgemeine Leistungen</KAPITEL>
<ABSCHNITT>
Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregel ung und Schwangerschaftsabbruch (vormals Sonstige Hilfen)
</ABSCHNITT>
<KURZTEXT>
Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a.
</KURZTEXT>
<LANGTEXT>
Grundpauschale für Fachärzte für Laboratoriumsmedizin, Mikrobiologie und Infektionsepidemiologi e, Transfusionsmedizin und ermächtigte Fachwissenschaftler der Medizin für die Erbringung von Laborleistungen gemäß den Richtlinien des Gemeinsamen Bundesauss
</LANGTEXT>
<QUITTUNGSTEXT>
Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a.
</QUITTUNGSTEXT>
<ANMERKUNG>
Die Leistung nach der Nr. 01100 ist nicht berechnungsfähig, wenn Sprechstunden vor 07:00 Uhr oder nach 19:00 Uhr stattfinden oder Patienten zu diesen Zeiten bestellt werden.
</ANMERKUNG>
</ROW>
<ROW num="2">
<ZIFFER>01700V</ZIFFER>
</ROW>
</ROWSET>
</page>

Problem with PDF content generated by CONVERT_OTF

Hi,
We are facing a problem with the version of the pdf content generated by FM CONVERT_OTF.
Data returned by this FM in the parameter BIN_FILE is in XSTRING or HexaDecimal Format.
As I am sending this PDF content to a Portal through RFC, they are unable to open the file in lower versions of Adobe.
The file is opened only in 8 and above versions of Adobe.
Is there anything which can be done in SAP so that the PDF content generated in SAP will be opened in the lower versions also.

Can you try with the belos stuff?
Converting to PDF
          CALL FUNCTION 'CONVERT_OTFSPOOLJOB_2_PDF'
            EXPORTING
              src_spoolid              = loc_spool (pass spool number here)
              no_dialog                = ' '
            IMPORTING
              pdf_bytecount            = numbytes
              pdf_spoolid              = pdfspoolid
              btc_jobname              = jobname
              btc_jobcount             = jobcount
            TABLES
              pdf                      = pdf
            EXCEPTIONS
              err_no_otf_spooljob      = 1
              err_no_spooljob          = 2
              err_no_permission        = 3
              err_conv_not_possible    = 4
              err_bad_dstdevice        = 5
              user_cancelled           = 6
              err_spoolerror           = 7
              err_temseerror           = 8
              err_btcjob_open_failed   = 9
              err_btcjob_submit_failed = 10
              err_btcjob_close_failed = 11.
Map PDF table into 'flat' table acording to Unicode flag
        LOOP AT pdf INTO wa_pdfline.
          ASSIGN wa_pdfline TO <l_xline> CASTING.
          CONCATENATE pdf_xstring <l_xline> INTO pdf_xstring IN BYTE MODE.
        ENDLOOP.
Use this PDF_XSTRING as the output of the RFC and same you can use it JAVA webdynpro. I hope this will provide the solution
Let me know if you still have any problem
Best Regards,
JR

Remote key for lookup tables

Hi,
I need some advice on remote keys for lookup tables.
We have loaded lookup data from several client system into the MDM repository. Each of the client system can have diffferences in the lookup values. What we need to do is to enable the keymappings so that the syndicator would know which value belongs to which system.
The tricky part is. We haven't managed to send out the values based on the remote keys. We do <b></b>not<b></b> want to send the lookup tables themselves but the actually main table records. All lookup data should be checked at the point of the syndication and only the used lookup values that orginally came from one system should be send to that particular system. Otherwise they should be tag should be blank.
Is this the right approach to handle this demand or is there a different way to take care of this? What would be the right settings in the syndicator?
Help will be rewarded.
Thank you very much
best regards
Nicolas

Hi Andreas,
that is correct. Let's take two examples:
1) regions
2) Sales Area data (qualified lookup data)
Both tables are filled and loaded directly from the R/3s. So you would already know which value belongs to which system.
The problem that I have is that we will not map the remote key from the main table because it will be blank for new created master data (Centralization scenario). Therefore we cannot map the remote key from the attached lookup tables, can we?
The remote key will only work for lookup tables if the remote key of the actual master data is mapped. Since we don't have the remote key (local customer ID form R/3) in MDM and since we do not create it at the point of the syndication... how would the SAP standard scenario would look like for that?
This is nothing extraordinary it's just a standard centralization scneario.
Please advice.
Thanks alot
best regards
Nicolas

Qualified Lookup Table in Webdynpro Content Generator

Similar Messages

Maybe you are looking for