Fm to read screen labels for country specific screens

Hi
Is there any funtion module to read the field labels from modulepool for country specific screens.
Thanks in advance

hi,
chk out this sample code:,
data: li_dynpfields type table of dynpread,
        lw_temp       like line of li_dynpfields.
        data: lv_molga like dynpread-fieldvalue,
         lv_para like dynpread-fieldvalue,
         lv_subty like dynpread-fieldvalue.
move 'P_MOLGA' to lw_temp-fieldname.
append lw_temp to li_dynpfields.
   move 'P_PARA' to lw_temp-fieldname.
append lw_temp to li_dynpfields.
   move 'P_SUBTY' to lw_temp-fieldname.
append lw_temp to li_dynpfields.
call function 'DYNP_VALUES_READ'
    exporting
      dyname               = sy-cprog
      dynumb               = sy-dynnr
      translate_to_upper   = ' '
    tables
      dynpfields           = li_dynpfields
    exceptions
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      others               = 11.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
clear lw_temp.
do 3 times.
read table li_dynpfields index sy-index into lw_temp.
if sy-index = 1.
lv_molga = lw_temp-fieldvalue.
elseif sy-index = 2.
lv_para = lw_temp-fieldvalue.
else.
lv_subty = lw_temp-fieldvalue.
endif.
enddo.
Regards,
Arunsri

Similar Messages

SAP support for country-specific legal requirements

Just wondering if anyone could clarify how does SAP support work for the country-specific legal requirements. I'm sure in every country some new laws come to life regularly that affect the SAP customers and their ERP systems.
Case in point - on July 1st Mexican authority SAT decided to ask businesses to send them some XML files with some GL account information ('Anexo 24' - see the announcement in Spanish here). The deadline for the first file submission is October 2014.
This clearly affects every single SAP customer in the whole Mexico, as well as potentially many North America customers who have manufacturing facilities there. So would it be reasonable to expect SAP to come up with some standard solution? XML file extraction doesn't seem to be incredibly complex to me (although I might be off).
Another question - how would the customers know that SAP is aware of new laws and is taking some action? Could there be an announcement posted somewhere? There is a website for SAP Latin Americabut the latest announcement there is from June and nothing else is on the home page except for the HANA ads. (My Spanish is limited to "dos cervezas por favor", sorry if I missed something.)
In absence of such communication, naturally, the only option the individual customers have is to send a message to SAP. And that's where SAP replies with a copy/paste text (we got the same exact response as another SCN member here):
Feel free to maintain this incident opened, but contact us in the next three weeks, then we will be able to confirm if this legal requirement will be supported by SAP.
I'm confused - "IF"?! This is a legal requirement, there is no "if" for the business. Let's see if I got it right - we wait for 3 weeks, then SAP decides "nah, not gonna support that" (by the way, why is it on the customers to contact support again?) and every SAP customer in the whole country will have to scramble their own resources or pay for consulting (on top of SAP maintenance fees) to deliver the same exact set of programs on their own in under 2 months?
It could've been just an unfortunate choice of verbiage by Global Support, but I'm curious - is this really how the support for legal requirements supposed to work?
Thank you.

Hi Jelena,
Having been part of the SAP Globalization Services in Brazil, I understand a little bit of that process.
A few comments:
1) Localization of SAP solutions to country-specific regulation is under the responsibility of an area called Globalization Services. You can find more info about what they do here:
http://service.sap.com/globalization
2) Typically, those country-specific requirements are discussed in much details on the local ASUG chapters (at least that's how we did it in Brazil). That's why it's usually hard to find material in English, but I'd say that your local IT/Biz people in Mexico should be regulars in their local ASUG meetings, specially if they have a specific chapter to discuss Localization matters.
3) I found out this note with more specifics about "SAT Anexo 24".
http://service.sap.com/sap/support/notes/2041490
Apparently SAP is still analyzing it.
Suggestion if you want to speed the analysis up: reach out to your commercial contact in SAP.
4) Regarding your statement about the time it takes for the analysis & delivery to take place.
As an SAP customer, you have all the right to complain about the service level you're getting, it's just that, having been on the other side of the table, I know some facts that sometimes may be taken for granted. For example, SAP do not have infinite maintenance resources. I do understand that all customers pay maintenance and need to have their demands addressed, but SAP does not have a bench of developers available for whenever a new demand appears. If there is a new demand, they need to estimate the efforts and accommodate it into the development resource planning.
5) From a legal perspective, there is a difference between Legal Change and New Legal Requirement. The latter, if differing too much from the initial purpose of the acquired software, might not necessarily be required by the Software provider to be fulfilled within the maintenance scope. I'm not saying that it's the case for this Mexican requirement, I'm just saying there is this possibility, generally.
My personal recommendation: get your local Mexico people to be closer to the SAP Mexico team. They are usually responsible to publish information about such local requirements and the SAP release plan.
Hope that helps.
Best,
Henrique.

HIDE AREAS FOR COUNTRY SPECIFIC ESS

Dear Expert.
I have the following issue.
In the company we have employees in several country. For one of this country some Areas ie. Career and Job will be not enabled.
I found issue similar and a solution in the following post:
[Applications of ESS |Applications of ESS]
In the previus post:
Bala Suggests
Do an implicit enhancement in this Fm HRXSS_SER_GETMENUDATA to hide the area for a particular country
Tiberiu Sasu Suggests:
You create two overview area group pages in the backend: ZAreaA and ZAreaB. ZAreaB does not contain the service link to Travel and Expenses
in roleA you configure the iView "Overview" to point to ZAreaA
in roleB you configure the iView "Overview" to point to ZAreaB
The question is:
If I use the option of Tiberiu, when the Basis Team do an update for the Business Package of ESS, we hot can have this update. ??
What is a best practice for solve this issue, having in count the SAP guidelines?
Thank in advance for your help.
Best Regards
Carmen

Hi,
I'd strongly agree with Bala.
The enhancement is relatively simple - I've done the same thing for several systems.
I have found, however, that the best way to drive the enhancement is by reading the user's security roles. This way access to the area can be granted/removed by the same process that grants access to any/every part of the system.
- Chris

How to Disable Country Specific Checking for IT0021

Hi
I'm implementing PA for three countries.
Client requires a common infotype be used across countries. For France and Italy I'm not able to set the IT0021 to the standard one. As SAP by default uses the Cpountry specific Infotpe.
How to Disable this feature of SAP.
- Aravind

use the same Screen for the rest of the countries
check P0021 in PE03
and check the number assigned to the screen
if u want the screen number check system status and module pool number
V_T582L for country specific
V_T588M this for Module pool
Edited by: Sikindar on Jan 16, 2009 8:54 AM

Report on country specific CoA

Hi All,
When trying to pull the report from S_ALR_87012282 for country specific Chart of Accounts, we are getting the following error:
"Company codes and charts of accounts entered are incompatible"
Here are the steps we did:
1. Assigned operational and country specific chart of account to ABCD at OBY6.
2. Created 2 accounts in operational chart of accounts. XXXXXXX & YYYYYYY
3. Created 2 accoutns in country specific chart of accoutns.XXX & YYY
4. Assigned XXX as alternative account to XXXXXXX and YYY to YYYYYYY
5. Posted a document using these accounts in F-02.
6. Ran a report to display the details w.r.t country specific CoA (S_ALR_87012282)
Here is when I got the error.
Can anyone please let me know what I am missing here..
All answers will be duly rewarded.
Thanks,
N

Hello
I am not sure if I understood your question right, but this is what I presume.
Yes, when you post to XXX a/c, the data is transferred to XXXXXX also.
There is no special validation, but enter XXXXXX in the master data of XXX a/c in the field ' Alternative account' in the control data.
Assuming the country specific chart of accounts would be using a seperate FSV, execute the report to check if the balance is transferred in the currency you desired.
Compare both financial statements, Assume you have seperate FSV for operative coa / country coa.
Reg
*Assign points if useful

Function Module or table to read all EQUI for one KUNNR

Hello,
i need to read all Equipments for one specific KUNNR (endcustomer).
Is there a function module which could be used?
Or what is a good select for this?
Thanks a lot.
Kind regards
Manfred

Hi,
EQBS table will be getting updated based on the Delivery document or while creating equipment for Material & Serial no combination.
How you are maintaining End Customer in your Equipment Master?
You can maintain in Partner Function or Sort Field or through automatic equipment creation.
Based on that, you have to find the logic.
Regards,
Maheswaran.

Kindly tell me some Examples of Country specific Infotypes?

Hi,
Kindly tell me some Examples of Country specific Infotypes?
Thanks,
Saurabh Garg

Search for country specific infotypes from
For more information, refer to the IMG for Personnel Management, under Personnel Administration ® Customizing Procedures ® Infotypes ® Assign Infotypes to Countries.
Refer this links
http://help.sap.com/saphelp_47x200/helpdata/en/9d/42d667133a11d2959600a0c94261c1/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/42/51c0744a1211d182b80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/86/1fc534d8df9b53e10000009b38f83b/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/48/35c4934abf11d18a0f0000e816ae6e/frameset.htm
Regds
Manohar

Is it possible to make a screen control appear only for a specific patch?

I use MainStage almost exclusively for guitar. Frequently I will use different guitar amps in different patches (usually the AmpliTube plugin, but occasionally Amp Designer). I'd like to use different screen controls for specific patches. For example, I might be using a Marshall JCM900 amp model for one patch, and a Vox AC-30 Top Boost amp model for a different patch. The Marshall has a gain control, and a master volume, but the AC-30 only has a master volume. Conversely, the AC-30 has a top cut control that doesn't exist on the Marshall.
Is there a way to hide the screen control for the Marshall gain on a patch that uses an AC-30 model?
It seems like there would be many, may scenarios where controls that are relevant to one patch would be undesirable with a different patch, but it seems like screen controls are global for an entire concert. Sure, a given control can be mapped to different parameters in different patches (but you can't give a screen control different names in different patches), but there's limited space on a layout, and it seems wasteful to have to provide a given screen control that might only be relevant for one patch out of a dozen in a given set or concert visible in every single patch.

Hi
Standard Screen Controls will always appear in Edit Mod and in Perform Mode for a given Concert. Controls that are not assigned to any parameter will be grayed out in Performance Mode. To do this, select the control in Edit, and choose "None" in the Screen Control Inspector.
Smart Controls adapt for a particular Patch. Different layouts can be assigned per patch.
ericmurphysf wrote:
you can't give a screen control different names in different patches)
That depends on the method you used to name them in the first place:
Controls can have different formats of labelling ( done in Layout mode), where they can show the particular parameter name etc etc. These can change from patch to patch.
You can assign a "Hardware Label" that is global.
Separate Text labels can have global or Set/Patch labels, and they can be labelled for a single Patch by overriding any higher level labelling
hth
CCT

Legal requirements for showing specific ESS screens in local language

Hi All,
I would appreciate if you can let me know if there is any legal requirements for showing specific screens in local language? I would also like to know which countries and what SAP ESS screens.
Thanks In Advance
Sunny

Good luck with that. I have never seen any "list of all countries" before like you are wanting. This will typically be part of your requirements gathering and blueprinting tasks.
Just one question....what is your "global template" for implementation and what is your scope for localization? That will dictate much of your work.

Redirect to country specific screen

I'm working on implementing the ESS service PZ02 (Change Address) for employees in Singapore. Many of the employees actually reside in Malaysia and other countries. When users change the country to something other than Singapore how can I send the user to the appropriate country specific screen? All employees are directed to HR_ESS_ADDRESSDETAIL_25 but screen 200 doesn't have a region field that Malaysia employees need to enter. Is it possible to send user to HR_ESS_ADDRESSDETAIL_14?

Hi Reid,
this is something you have to do by changeing the ABAP code. It would not make sense to do such customization on ITS level.
With kind regards,
Klaus

Copy Standard infotype screen for country purpose

Hi,
I am trying to copy the Standard screen (2007) for the infotype IT0002 to make some country specific modification.
However I am not able to copy the standard screen as it is asking for the Access Key.
Can you please suggest if there is a way to copy the standard infotype screen without providing the access key.
Regards
Bharath

Hi,
Why don't you just enhance the infotype via PM01 - Enhance single screen?
(MP000200 screen 2007)
Regards,
Dilek
Edited by: Dilek Ersoz Adak on Feb 8, 2010 6:53 PM

Disabling country specific checkings for it 0021

Although we are a german-based company and only do german payroll, we still have to maintain personal records from our employees all over the world, mainly for reporting purposes. Last week someone from our HR-staff tried to create it 0021 subtype 1 (spouse), but just can't manage to get it work. Some debugging showed me, that a class CL_HRPA_INFOTYPE_0021_ES with method CHECK_NIF_CONYUGE_REPRESENTANT is called and throws an error. I haven't figured out what is checked, but I definetly don't want any checking at all. Are there any means to disable this country specific checking (customizing ???).

Hi Shrinivas
The messagenumber is 5E048:
El valor no está permitido para el parámetro
According to babelfish.yahoo.com this means:
The value is not allowed for the parameter
well, that's the truth from SAP's point of view, because the afore mentionend
method checks the subtype against t5e91:
method CHECK_NIF_CONYUGE_REPRESENTANT .
data: wa_t5e91 type t5e91,
         l_msg TYPE symsg.
select single * from t5e91 into wa_t5e91
where infty eq '0021' and
        subty eq p_subty.
if wa_t5e91-isfam eq 'C' or wa_t5e91-isfam eq 'R'.
    if p_codim is initial.
      CLEAR l_msg.
      l_msg-msgid = '5E'.
      l_msg-msgty = 'E'.
      l_msg-msgno = '048'.
      CALL METHOD message_handler->add_message
        EXPORTING
          message = l_msg
          cause   = if_hrpa_message_handler=>infotype_specific.
      is_ok = false.
    endif.
endif.
endmethod.
What I need to achieve is, that class CL_HRPA_INFOTYPE_0021_ES isn't called at all, so no checking is done.

Call Country Specific Screen in ESS

Hi experts,
I am customizing the ESS Address,want to call country specific screens.How can I call country specific address screen for different countries?
How SAP call the country specific screen based on contry?
Thanks&Regards,
vino
Edited by: vino on Dec 3, 2008 11:57 PM

Hi,
What is this molga ?
Can anyone explain in detail how to acheive country specific scenarios ( like if i want some UI elements to be visible for one country but not for other )?
Can this be achieved from the backend settings (spr) in homepage framework or we need to do changes by going into the UI ?
If changes are to be done by going into UI then do we need to create seperate iviews for each country ?
Regards,
Indu

How to set a MessageTextInput to be Read Only for a specific row?

Hi,
In Benefits Self Service, particularly the Update Beneficiaries page, it lists all your eligible Beneficiaries including yourself. The table has the following columns displayed for each beneficiary: Beneficiary, Relationship, Social Security Number, Primary %, Contingent %, Clear. This is the page where you allocate the Primary % and the Contingent %. The Primary % and Contingent % are MessageText Input.
We have a requirement that we wouldn't want an employee to designate himself/herself as a beneficiary. However, the employee is being listed as a beneficiary along with all the other eligible beneficiaries. Oracle says it is an intended functionality to include the employee in the beneficiary. Is there a way thru Controller Object extension to set the Primary % and Contingent % as Read Only but only for the row corresponding to the employee to prevent the employee from accidentally allocating himself/herself as a beneficiary.
I know there is the SPEL functionality but this requires me to add a transient attribute to the View Object corresponding to that table. But everytime I make a change to the View Object either by adding a transient attribute or some other changes, I end up getting an error on the standard Relation attribute of that view object. The error is something like "Relation set attribute failed for View Object". I cannot get pass this error and I'm not sure what's causing this. I see other people in this forum have encountered the same problem when extending view objects but no specific solution was offered nor any clear explanation of the cause.
So I thought if there's any way this could be done thru Controller Object extension. If so, please let me know how. The challenge for me I think is finding the bean corresponding to those Message Text Input but only for a specific row in the table.
Thanks,
Ronaldo

Hi,
I also tried extending the View Object but without changing anything to the SQL so it is exactly the same as the standard view object but I still get the "Attribute set for Relation in view object BeneficiaryPeopleVO1 failed". Based from this, extending the view object whether any change has been made or not affects the standard transient Relation attribute.
Here is the standard XML definition of the View Object if anyone is curious
<ViewObject
Name="BeneficiaryPeopleVO"
BindingStyle="Oracle"
CustomQuery="true"
RowClass="oracle.apps.ben.selfservice.enrollment.server.BeneficiaryPeopleVORowImpl"
ComponentClass="oracle.apps.ben.selfservice.enrollment.server.BeneficiaryPeopleVOImpl"
MsgBundleClass="oracle.jbo.common.JboResourceBundle"
FetchMode="FETCH_AS_NEEDED"
FetchSize="10"
UseGlueCode="false" >
<SQLQuery><![CDATA[
SELECT pcr.person_id person_id,
pen.prtt_enrt_rslt_id prtt_enrt_rslt_id,
con.first_name ||' '||con.last_name || ' ' || con.suffix Beneficiary,
con.national_identifier Ssn,
sum(decode(pbn.prmry_cntngnt_cd,'PRIMY',pbn.pct_dsgd_num,0)) primary_pct,
sum(decode(pbn.prmry_cntngnt_cd,'CNTNGNT',pbn.pct_dsgd_num,0)) contingent_pct,
con.person_id bnf_person_id,
con.business_group_id,
pen.per_in_ler_id,
pbn.pl_bnf_id pl_bnf_id,
pbn.object_version_number object_version_number,
pbn.effective_start_date,
pcr.contact_type contact_type,
con.full_name beneficiary_full_name,
sum(decode(pbn.prmry_cntngnt_cd,'PRIMY',pbn.pct_dsgd_num,0)) Db_Primary_pct,
sum(decode(pbn.prmry_cntngnt_cd,'CNTNGNT',pbn.pct_dsgd_num,0)) db_contingent_pct,
DECODE(pbn.pl_bnf_id, null, 'DeleteIconDisabled', 'DeleteIconEnabled') delete_switcher,
pen.pl_id pl_id,
pen.oipl_id oipl_id,
nvl((select 'Y' from dual where (to_date(:1 , 'rrrr/mm/dd') between
          nvl(pcr.date_start,to_date(:2 , 'rrrr/mm/dd')) and
          nvl(pcr.date_end,to_date(:3 , 'rrrr/mm/dd'))) and
          (pil.lf_evt_ocrd_dt <= nvl(con.date_of_death,pil.lf_evt_ocrd_dt))), 'N') rel_exists_flag
FROM per_people_f con,
per_contact_relationships pcr,
ben_pl_bnf_f pbn,
ben_prtt_enrt_rslt_f pen,
     ben_per_in_ler pil
WHERE pcr.personal_flag = 'Y'
AND (pbn.pl_bnf_id is not null or
(to_date(:4 ,'rrrr/mm/dd') between
nvl(pcr.date_start,to_date(:5 ,'rrrr/mm/dd'))
AND nvl(pcr.date_end,to_date(:6 ,'rrrr/mm/dd'))
          and pil.lf_evt_ocrd_dt <= nvl(con.date_of_death,pil.lf_evt_ocrd_dt)))     --Bug 4297137
AND pcr.contact_person_id = con.person_id
and pen.person_id = pcr.person_id
AND pbn.bnf_person_id (+) = con.person_id
AND to_date(:7 ,'rrrr/mm/dd') between pbn.effective_start_date (+)
AND pbn.effective_end_date (+)
AND pcr.person_id = :8
and pen.prtt_enrt_rslt_id = :9
and to_date(:10 , 'rrrr/mm/dd') between con.effective_start_date and con.effective_end_date
and to_date(:11 , 'rrrr/mm/dd') between pen.effective_start_date and pen.effective_end_date
and pil.per_in_ler_id = pen.per_in_ler_id
and pil.per_in_ler_stat_cd NOT IN('VOIDD', 'BCKDT')
and pbn.prtt_enrt_rslt_id (+) = :12
and ((to_date(:13 ,'rrrr/mm/dd') between
nvl(pcr.date_start,to_date(:14 ,'rrrr/mm/dd')) and
nvl(pcr.date_end,to_date(:15 ,'rrrr/mm/dd'))) or
((pcr.date_start = (select max(pcr2.date_start)
from per_contact_relationships pcr2
where pcr2.contact_person_id = pcr.contact_person_id
and pcr2.person_id = pcr.person_id
and pcr2.personal_flag = 'Y')) and
not exists (select null
from per_contact_relationships pcr3
where pcr3.contact_person_id = pcr.contact_person_id
and pcr3.person_id = pcr.person_id
and pcr3.personal_flag = 'Y'
and to_date(:16 ,'rrrr/mm/dd') between
nvl(pcr3.date_start,to_date(:17 ,'rrrr/mm/dd'))
and nvl(pcr3.date_end,to_date(:18 ,'rrrr/mm/dd')))
and (pbn.pl_bnf_id is null or
exists (select null from ben_per_in_ler pil2
where pil2.per_in_ler_id = pbn.per_in_ler_id
and pil2.per_in_ler_stat_cd not in ('VOIDD','BCKDT')))
GROUP BY pcr.person_id,
pen.prtt_enrt_rslt_id,
con.last_name,con.first_name,con.suffix,
con.full_name,
con.national_identifier,
pcr.contact_type,
con.date_of_birth,
con.person_id,
con.business_group_id,
pen.per_in_ler_id,
pl_bnf_id,
pbn.object_version_number,
pbn.effective_start_date,
pen.pl_id,
pen.oipl_id,
          pcr.date_start,
          pcr.date_end,
          pil.lf_evt_ocrd_dt,
          con.date_of_death
union
SELECT to_number(null) person_id,
pen.prtt_enrt_rslt_id prtt_enrt_rslt_id,
con.first_name ||' '||con.last_name || ' ' || con.suffix Beneficiary,
con.national_identifier Ssn,
sum(decode(pbn.prmry_cntngnt_cd,'PRIMY',pbn.pct_dsgd_num,0)) primary_pct,
sum(decode(pbn.prmry_cntngnt_cd,'CNTNGNT',pbn.pct_dsgd_num,0)) contingent_pct,
con.person_id bnf_person_id,
con.business_group_id,
pen.per_in_ler_id,
pbn.pl_bnf_id pl_bnf_id,
pbn.object_version_number object_version_number,
pbn.effective_start_date,
'SLF' contact_type,
con.full_name beneficiary_full_name,
sum(decode(pbn.prmry_cntngnt_cd,'PRIMY',pbn.pct_dsgd_num,0)) Db_Primary_pct,
sum(decode(pbn.prmry_cntngnt_cd,'CNTNGNT',pbn.pct_dsgd_num,0)) db_contingent_pct,
DECODE(pbn.pl_bnf_id, null, 'DeleteIconDisabled', 'DeleteIconEnabled') delete_switcher,
pen.pl_id pl_id,
pen.oipl_id oipl_id,
'Y' rel_exists_flag
FROM per_people_f con,
ben_pl_bnf_f pbn,
ben_prtt_enrt_rslt_f pen,
     ben_per_in_ler pil
WHERE
pbn.bnf_person_id (+) = con.person_id
AND to_date(:19 ,'rrrr/mm/dd') between pbn.effective_start_date (+)
AND pbn.effective_end_date (+)
AND con.person_id = :20
and con.person_id = pen.person_id
and pen.prtt_enrt_rslt_id = :21
and to_date(:22 , 'rrrr/mm/dd') between con.effective_start_date and con.effective_end_date
and to_date(:23 , 'rrrr/mm/dd') between pen.effective_start_date and pen.effective_end_date
and pil.per_in_ler_id = pen.per_in_ler_id
and pil.per_in_ler_stat_cd NOT IN('VOIDD', 'BCKDT')
and (pbn.pl_bnf_id is not null or pil.lf_evt_ocrd_dt <= nvl(con.date_of_death,pil.lf_evt_ocrd_dt))     --Bug 4297137
and pbn.prtt_enrt_rslt_id (+) = :24
and (pbn.pl_bnf_id is null or
exists (select null from ben_per_in_ler pil2
where pil2.per_in_ler_id = pbn.per_in_ler_id
and pil2.per_in_ler_stat_cd not in ('VOIDD','BCKDT')))
GROUP BY pen.prtt_enrt_rslt_id,
con.last_name,con.first_name,con.suffix,
con.full_name,
con.national_identifier,
con.date_of_birth,
con.person_id,
con.business_group_id,
pen.per_in_ler_id,
pl_bnf_id,
pbn.object_version_number,
pbn.effective_start_date,
pen.pl_id,
pen.oipl_id
ORDER BY 3,14
]]></SQLQuery>
<DesignTime>
<Attr Name="_isCodegen" Value="true" />
<Attr Name="_version" Value="9.0.3.13.75" />
<Attr Name="_CodeGenFlagNew" Value="36" />
<Attr Name="_rowSuperClassName" Value="oracle.apps.fnd.framework.server.OAPlsqlViewRowImpl" />
<Attr Name="_objectSuperClassName" Value="oracle.apps.fnd.framework.server.OAPlsqlViewObjectImpl" />
</DesignTime>
<ViewAttribute
Name="PersonId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PERSON_ID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="PrttEnrtRsltId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PRTT_ENRT_RSLT_ID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="Beneficiary"
IsQueriable="false"
IsPersistent="false"
Precision="332"
Type="java.lang.String"
AliasName="BENEFICIARY"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="VARCHAR" >
</ViewAttribute>
<ViewAttribute
Name="Ssn"
IsQueriable="false"
IsPersistent="false"
Precision="30"
Type="java.lang.String"
AliasName="SSN"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="VARCHAR" >
</ViewAttribute>
<ViewAttribute
Name="PrimaryPct"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Type="oracle.jbo.domain.Number"
AliasName="PRIMARYPCT"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="ContingentPct"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="CONTINGENTPCT"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="BnfPersonId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="BNFPERSONID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="BusinessGroupId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="BUSINESSGROUPID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="PerInLerId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PERINLERID"
ColumnType="$none$"
Expression="'See the SQL...'"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="PlBnfId"
IsQueriable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PL_BNF_ID"
ColumnType="$none$"
Expression="PL_BNF_ID"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="ObjectVersionNumber"
IsQueriable="false"
IsPersistent="false"
Precision="9"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="OBJECT_VERSION_NUMBER"
ColumnType="$none$"
Expression="OBJECT_VERSION_NUMBER"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="EffectiveStartDate"
IsQueriable="false"
IsPersistent="false"
Type="oracle.jbo.domain.Date"
AliasName="EFFECTIVE_START_DATE"
ColumnType="$none$"
Expression="EFFECTIVE_START_DATE"
SQLType="DATE" >
</ViewAttribute>
<ViewAttribute
Name="ContactType"
IsQueriable="false"
IsPersistent="false"
IsNotNull="true"
Precision="30"
Type="java.lang.String"
AliasName="CONTACT_TYPE"
ColumnType="$none$"
Expression="CONTACT_TYPE"
SQLType="VARCHAR" >
<DesignTime>
<Attr Name="_DisplaySize" Value="30" />
</DesignTime>
</ViewAttribute>
<ViewAttribute
Name="BeneficiaryFullName"
IsQueriable="false"
IsPersistent="false"
Precision="240"
Type="java.lang.String"
AliasName="BENEFICIARY_FULL_NAME"
ColumnType="$none$"
Expression="BENEFICIARY_FULL_NAME"
SQLType="VARCHAR" >
<DesignTime>
<Attr Name="_DisplaySize" Value="240" />
</DesignTime>
</ViewAttribute>
<ViewAttribute
Name="DbPrimaryPct"
IsQueriable="false"
IsPersistent="false"
Type="oracle.jbo.domain.Number"
AliasName="DB_PRIMARY_PCT"
ColumnType="$none$"
Expression="DB_PRIMARY_PCT"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="DbContingentPct"
IsQueriable="false"
IsPersistent="false"
Type="oracle.jbo.domain.Number"
AliasName="DB_CONTINGENT_PCT"
ColumnType="$none$"
Expression="DB_CONTINGENT_PCT"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="Relation"
IsQueriable="false"
IsPersistent="false"
Type="java.lang.String"
AliasName="Relation"
ColumnType="$none$"
SQLType="VARCHAR" >
</ViewAttribute>
<ViewAttribute
Name="DeleteSwitcher"
IsPersistent="false"
Precision="30"
Type="java.lang.String"
AliasName="DeleteSwitcher"
ColumnType="VARCHAR2"
Expression="DeleteSwitcher"
SQLType="VARCHAR" >
</ViewAttribute>
<ViewAttribute
Name="PlId"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="PlId"
ColumnType="VARCHAR2"
Expression="PlId"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="OiplId"
IsUpdateable="false"
IsPersistent="false"
Precision="15"
Scale="0"
Type="oracle.jbo.domain.Number"
AliasName="OiplId"
ColumnType="VARCHAR2"
Expression="OiplId"
SQLType="NUMERIC" >
</ViewAttribute>
<ViewAttribute
Name="RelExistsFlag"
IsQueriable="false"
IsPersistent="false"
Precision="30"
Type="java.lang.String"
AliasName="REL_EXISTS_FLAG"
ColumnType="VARCHAR2"
Expression="REL_EXISTS_FLAG"
SQLType="VARCHAR" >
</ViewAttribute>
</ViewObject>
Thanks,
Ronaldo

Since downloading the most current iTunes software I can no longer print the insert (label) for a jewel case. The songs are printed over each other and can not be read. Any suggestions? Thanks.

Since downloading the most current iTunes software I am no longer able to print an insert (label) for a jewel case. I click on print, choose jewel case and then it doesn't matter which option I choose for the insert it will only print the songs over each other in a 1 inch section so that it can not be used or read. If instead of clicking on the jewel case I click on list it works fine and prints an appropriate list. I have always updated the iTunes software the first time I am offered to do so and I have never had a problem printing the jewel case inserts. Since this issue is not about a piece of hardware iTunes help will not help me.

Did you ever get a response?
If you so how did you correct the problem?
I have the exact problem you had.
Please let me know.
Thank you
<Edited by Host>

Fm to read screen labels for country specific screens

Similar Messages

Maybe you are looking for