Explanation of terms

Hi
I am a student and I have to write a report on Java Beans and RMI and I am a little confused on the diferent terminology and was hoping that someone could help me out. Here is what I can gather from reading all the info that I have found so far.
When talking about a JavaBan it refers to a Java Class designed to conform to the JavaBean specification that turns them into a re-usable software component that can be used in application builders. Generally these are graphical type GUI tools like enhanced test boxes etc, that are used to build client side GUIs, but they don't have to be. Any Java class can be turned into a Bean as long as it conforms to the Bean specification, so this means that a class that encapsulates some type of business logic could also be turned into a bean. Is this correct?
Java RMI is another specification that allows beans to become remotely accessble objects, used for distributed computing. This is where I become unstuck. Do the beans need to be re-written to conform to the RMI specification or is the RMI object seperate to the Bean? Can you use a standard Javabean as a distributed object?
How do Enterprise JavaBeans fit into all this?
If anyone can explain this to me I would be geatly appreciated.
Regards
Andrew

I am myself a beginner in that technology so that I'll respond with the best of my knowledge.
Any Java class can be turned into a
Bean as long as it conforms to the Bean specification,
so this means that a class that encapsulates some type
of business logic could also be turned into a bean. Is
this correct?
Yes.
Java RMI is another specification RMI isn't only a specification. It's a technology/API that lets you execute on a local computer code that is on another (remote) computer through the network. It's a java-specific RPC (Remote Procedure Call) mechanism.
that allows beans to
become remotely accessble objects, used for
distributed computing.
Do the beans need to be re-written to conform to the
RMI specification or is the RMI object seperate to the
Bean? Can you use a standard Javabean as a distributed
object?
How do Enterprise JavaBeans fit into all this?
If anyone can explain this to me I would be geatly
appreciated.
Regards
AndrewRMI itself doesn't require that remotely accessible objects are beans and doesn't prevent them to be so. It isn't much more than a transport and communication mechanism.
EJB is quite different because it's a design and architecture specification for client-server and distributed applications. EJB can be implemented using RMI or using other transport and communication systems, like CORBA.

Similar Messages

Explanation regarding terms and code

hi
i am new to webdynpro for java, i cant understant the terms used in the below coding.
1. wdcontext
2. iwdmessagemanager
etc, can any one explain me in detail wats happening in the below code.
Request_SendEmail requestMO = wdContext.currentRequest_SendEmailElement().modelObject();
requestMO.wdSetInvocationLogEnabled( logger.beDebug() ? true : false);
try {
// call Email Web Service and update dependent // model node 'Response'
wdContext.currentRequest_SendEmailElement() .modelObject().execute();
wdContext.nodeResponse().invalidate();
BigDecimal returnCode =
wdContext.currentSendEmailResponseElement().getReturnCode();
String msg = "Email Web Service returned " + returnCode.toString();
if (returnCode.intValue() == 0) {
msgMgr.reportSuccess("Your email was successfully sent (" + msg + ")!");
} else {
msgMgr.reportWarning(
"Your email was not successfully sent (" + msg + ")!");
} catch (CMIException ex) {
msgMgr.reportException(ex.getLocalizedMessage(), true);
this.logWSInvocation(requestMO, ex);
//@@end
thanks in advance
rick

Hi ricky,
According to ur program
context is a virtual memory it is used to store value of the ui element.
iwdmessagemanager is used to print some error messages from message pool(or)if we want to know the values we can use that as print statemant like (Sys.out.print) in java(report success is used for that)
//creating model object for Request_SendEmail
Request_SendEmail requestMO = wdContext.currentRequest_SendEmailElement().modelObject();
//ur checking beDebug()method is true or false according to that InvocationLogEnabled value is set.
requestMO.wdSetInvocationLogEnabled( logger.beDebug() ? true : false);
try {
// call Email Web Service and update dependent // model node 'Response'
//here ur executing the model so that the values r initilized.
wdContext.currentRequest_SendEmailElement() .modelObject().execute();
//invalidate() is used to clear the values.that is ur clearing the response node values.
wdContext.nodeResponse().invalidate();
//here ur accessing SendEmailResponse ReturnCode that is to be stored as BigDecimal type.
BigDecimal returnCode =
wdContext.currentSendEmailResponseElement().getReturnCode();
//ur adding returnCode value to the string
String msg = "Email Web Service returned " + returnCode.toString();
//According to the return code ur printing messages whether it is successful or not.
if (returnCode.intValue() == 0) {
msgMgr.reportSuccess("Your email was successfully sent (" + msg + ")!");
} else {
msgMgr.reportWarning(
"Your email was not successfully sent (" + msg + ")!");
} catch (CMIException ex) {
msgMgr.reportException(ex.getLocalizedMessage(), true);
this.logWSInvocation(requestMO, ex);
//@@end

Wireless packet flow explanation

Hi My requirement is very simple , I will appreciate if someone can explain me the following concept as per the diagram mentioned below
I have 2 APs AP1 and AP2, both connect to switch on port f0/1 and f0/2 , the switch f0/3 inturn connects to a router on f0/0 , router's interface f0/1 connects to another switch which is wired network with ip add 192.168.2.0/24 .
1. APs broadcast 3 ssid (management , guest , cisco) respectively , how would the data flow happen for user connected to SSID cisco when pings another user connected to SSID guest , and how would data flow happen when user in SSID cisco ping a user 192.168.1.100 some user is wired network.
you can assume both the APs are autonomous and there is no controller.
I am looking for explanation in terms of frame tagging and packet encapsulation and depacsulation at various stages.
you can assume the IP nd vlan number on wireless network as you like.
2.if you are not tired yet then one mroe question with same topology , but this time the APs are lightweight and the controller is in a different subnet 192.168.1.0 , assume that the AP is already registered with controller , now how would the same above communication happen ,
I am looking for explanation in terms of frame tagging and packet encapsulation and depacsulation at various stages.
you can assume the IP and vlan number on wireless network as you like.
If you can refer me some doc its fine with me , I already went through many documents and nuggets , I do have a clear picture.
Thank you

1.
client to AP ===> 802.11 frame.
AP to client ===> 802.11 frame. At AP, received wired side ethernet frame removes the ethernet header with tag and encapsulates the IP packet using 802.11 header with right Bssid for that vlan.
AP ethernet to switch interface ===> Tag/UnTag Ethernet frame. At AP, received 802.11 frames removes the 802.11 mac header, the inner packet will be used to encapsulate using ethernet frame with Tag based on received Bssid.
ARP request - Broadcast packet sent by wireless client to AP as unicast. Once it decapsulates the 802.11 header, the inner IP packet hits the wire on that broadcast domain to reach upstream wired switch and wireless on same AP.
2.
AP to WLC ===> capwap/lwapp. 802.11 packets are encapsulated on L3 IP-UDP.
WLC to AP ===> capwap/lwapp.
All the client (802.11) packets are encapsulated in a LWAPP packet by the LAP and sent to the WLC. WLC descapsulates the LWAPP packet and acts based on the destination IP address in the 802.11 packet. If the destination is one of the wireless clients associated to the WLC, it encapsulates the packet again with the LWAPP and sends it to the LAP of the client, where it is decapsulated and sent to the wireless client. If the destination is on the wired side of the network, it removes the 802.11 header, adds the Ethernet header, and forwards the packet to the connected switch, from where it is sent to the wired client. When a packet comes from the wired side, WLC removes the Ethernet header, adds the 802.11 header, encapsulates it with LWAPP, and sends it to the LAP, where it is decapsulated, and the 802.11 packet is delivered to the wireless client
check:-
https://supportforums.cisco.com/message/3489064#3489064
https://supportforums.cisco.com/message/3717713#3717713

Maintain table TVZBT in other languages (payment terms)

Hi All,
I try to maintain the table TVZBT (languages of payment terms) using the OBB8 transaction.
I do log on in spanish, go to OBB8 and try to maintain the description in portuguese (in GO TO, TRADUCTION) and I maintain PT languages.
But when I save it, the table was not maintained.
If I do log on in portuguese, and go to OBB8 to maiantain this description, then this will be maintained in PT in the table TVZBT.
Someone know how to maintain the languages in this table?? I can't install all the languages in SAP to do log on in all of them.
Regards,
Ale.

I don't think with above steps you can updated language in Table TVZBT. Through those steps you will update this in Table T052U - Own Explanations for Terms of Pay, which you can use in respective outputs.
Refer following SAP Notes, which talks about a SAP Report RVZTERM(Match Terms of Payment TVZB/T vs. T052) which compares above mention tables & creates missing texts in the TVZBT.
- 6571 - Compare payment terms in TVZB/T with T052
- 131999 - RVZTERM only selects customers
If that does help you, better raise a ticket with SAP.
Thanks, JP

PNPCE - Obsolete Statements

Hi,
I am using PNPCE logical data base in my prog.
For this I defined the following.
Nodes: Peras.
Tables: Pernr.
Infotypes: 0002.
Is it mandatory to use Tables: Pernr. (Without this selection-screen is not coming)?
Also the statement Infotypes is Obsolete. Any alternate for this?
This statement creates infotype internal tables with header line which is not supported in OO context.
So what is the alternate for this?
Still lot of obsolete statements are shown in extended check even if I use PNPCE.
How to replace them?

hi read this ..will use ful for you.......
Purpose
The PNPCE logical database supports the evaluation of HR master data. It includes the functions of the PNP logical database and offers additional evaluation options. Therefore, you should use the PNPCE logical database instead of the PNP logical database for all new developments.
The enhanced functionality of PNPCE in comparison to PNP essentially concerns the evaluation of Concurrent Employment, that is the possibility to group evaluate several assignments/personnel numbers of a person. The new events 'GET PERSON' and 'GET GROUP' as well as an enhanced syntax for the INFOTYPES statement (addition AS PERSON TABLE) for the procurement of infotype data enable you to use the new functionality. The use of these new functions is optional. You can run a PNPCE report that does not use the new events and the addition for the INFOTYPES statement in a PNP-compatible session. Since the PNPCE also has an improved selection screen, each report benefits from this even if the report does not use the functions for evaluating Concurrent Employment.
Prerequisites
A report that wants to use the PNPCE must enter this in its report attributes under Logical database.
In addition, the PERNR structure must be declared in the report using the 'TABLES PERNR' statement. You can only use the PERNR structure again in certain circumstances. The use of the 'GET PERNR' event is therefore forbidden. Instead, use the 'GET PERAS' event. Except for the PERNR-PERNR component, all other components of the PERNR structure are no longer filled and have initial values. This kind of programming (with the exception of PERNR-PERNR) therefore not permitted.
In addition to the 'GET PERAS' event, you can also use the GET PERSON' and 'GET GROUP' events. To be able to use these events, you must declare them using the NODES statement (NODES PERSON', 'NODES GROUP', or. NODES PERAS').
Explanation of Terms
If the 'GET PERSON' and 'GET GROUP events and the 'AS PERSON TABLE' addition for the INFOTYPES statement are not used, the report indicates that it does not require the functionality for evaluating Concurrent Employment. In this case, the report runs in a PNP-compatible session. This is referred to as PNP mode in the following documentation. On the other hand, if the report uses the functionality for evaluating Concurrent Employment we refer to CE mode.
Features
Process of an Evaluation
The PNPCE selection screen offers you as standard a range of functions that you can use to restrict the personnel number and person selection. These are discussed in more detail in the following sections. The process is initially as follows regardless of whether the report runs in CE or PNP mode. All available functions and selection conditions leads to the selection of personnel numbers. If you use the sorting function, this set of personnel numbers is then sorted according to the sort criteria you selected. In PNP mode, the GET PERAS event is triggered as a result for each personnel number.
In CE mode, the persons belonging to the personnel numbers are determined first for all personnel numbers selected. The GET PERSON event is then triggered for each person. The person ID is specified in the OBJID component of the PERSON structure. PERNR_NUM contains the total number of personnel assignments (= personnel numbers) that this person has and the ALL_PERNRS table, which contains a list of these personnel numbers regardless of whether they were actually selected or not. The SELECTED flag is set to X for the personnel numbers selected. The flag is initial for all personnel numbers that are not selected. The PROCESS flag specifies whether the personnel number should be processed in the rest of the process. This flag is set to X by default for the personnel numbers selected. However, the report can set or delete this flag at the GET PERSON event for all personnel numbers. In this way, report and logical database communicate with each other which enables the report to control the rest of the process.
In the next step, the logical database groups all personnel numbers of a person that are to be processed (that is, all personnel numbers that have the PROCESS flag set). The report can control the type of grouping using the PNPCE_GROUPING_FROM_PAYROLL flag (normal or payroll grouping) and using the PNPGPRSN (grouping reason) and PNPGPVAL (grouping value) parameters of the selection screen. The GET GROUP event is triggered for each group of personnel numbers determined. The GROUPING_REASON and GROUPING_VALUE components contain the grouping reason and grouping value of this group. The number of personnel numbers that belong to this group and that are processed subsequently is in PERNR_NUM. The included ALL_PERNR table contains a list of these personnel numbers with additional information. The SELECTED flag specifies whether the current personnel number was originally selected (flag is set) or was marked by the report as to be processed. GROUPING_BEGDA and GROUPING_ENDDA contain the validity period that the personnel number has for this grouping. The NO_AUTHORITY flag is set if there is insufficient authorization for a personnel number. This personnel number is not processed further. The SORT component defines a standard sort order for the personnel numbers of a group. The report can change this by overwriting the values. In this way, report and logical database communicate with each other, which controls the further processing sequence of the personnel numbers.
The GET PERAS event is then triggered for all personnel numbers of the group (with the exception of the personnel numbers for which no authorization exists) in the sequence defined by the SORT component (see above). The SELECTED, GROUPING_BEGDA, and GROUPING_ENDDA components have the same meaning here as with the GET GROUP event. The PROCESSED_BEFORE flag specifies whether the personnel number has already been processed once before (it is possible that the personnel number belongs to several groupings and has been therefore been processed several times).

Concurrent Employment

We have concurrent employment maintained in our project. I need to develop reports based on PNPCE LDB. I wanted to know major differences between PNP and PNPCE and various pitfalls while using PNPCE LDB.

hi,
check the differences between pnp and pnpce in se36 transaction.
RE SAPDBPNPCE
Text
HR Master Data (Incl. Concurrent Employment)
Purpose
The PNPCE logical database supports the evaluation of HR master data. It includes the functions of the PNP logical database and offers additional evaluation options. Therefore, you should use the PNPCE logical database instead of the PNP logical database for all new developments.
The enhanced functionality of PNPCE in comparison to PNP essentially concerns the evaluation of Concurrent Employment, that is the possibility to group evaluate several assignments/personnel numbers of a person. The new events 'GET PERSON' and 'GET GROUP' as well as an enhanced syntax for the INFOTYPES statement (addition AS PERSON TABLE) for the procurement of infotype data enable you to use the new functionality. The use of these new functions is optional. You can run a PNPCE report that does not use the new events and the addition for the INFOTYPES statement in a PNP-compatible session. Since the PNPCE also has an improved selection screen, each report benefits from this even if the report does not use the functions for evaluating Concurrent Employment.
Prerequisites
A report that wants to use the PNPCE must enter this in its report attributes under Logical database.
In addition, the PERNR structure must be declared in the report using the 'TABLES PERNR' statement. You can only use the PERNR structure again in certain circumstances. The use of the 'GET PERNR' event is therefore forbidden. Instead, use the 'GET PERAS' event. Except for the PERNR-PERNR component, all other components of the PERNR structure are no longer filled and have initial values. This kind of programming (with the exception of PERNR-PERNR) therefore not permitted.
In addition to the 'GET PERAS' event, you can also use the GET PERSON' and 'GET GROUP' events. To be able to use these events, you must declare them using the NODES statement (NODES PERSON', 'NODES GROUP', or. NODES PERAS').
Explanation of Terms
If the 'GET PERSON' and 'GET GROUP events and the 'AS PERSON TABLE' addition for the INFOTYPES statement are not used, the report indicates that it does not require the functionality for evaluating Concurrent Employment. In this case, the report runs in a PNP-compatible session. This is referred to as PNP mode in the following documentation. On the other hand, if the report uses the functionality for evaluating Concurrent Employment we refer to CE mode.
Features
Process of an Evaluation
The PNPCE selection screen offers you as standard a range of functions that you can use to restrict the personnel number and person selection. These are discussed in more detail in the following sections. The process is initially as follows regardless of whether the report runs in CE or PNP mode. All available functions and selection conditions leads to the selection of personnel numbers. If you use the sorting function, this set of personnel numbers is then sorted according to the sort criteria you selected. In PNP mode, the GET PERAS event is triggered as a result for each personnel number.
In CE mode, the persons belonging to the personnel numbers are determined first for all personnel numbers selected. The GET PERSON event is then triggered for each person. The person ID is specified in the OBJID component of the PERSON structure. PERNR_NUM contains the total number of personnel assignments (= personnel numbers) that this person has and the ALL_PERNRS table, which contains a list of these personnel numbers regardless of whether they were actually selected or not. The SELECTED flag is set to X for the personnel numbers selected. The flag is initial for all personnel numbers that are not selected. The PROCESS flag specifies whether the personnel number should be processed in the rest of the process. This flag is set to X by default for the personnel numbers selected. However, the report can set or delete this flag at the GET PERSON event for all personnel numbers. In this way, report and logical database communicate with each other which enables the report to control the rest of the process.
In the next step, the logical database groups all personnel numbers of a person that are to be processed (that is, all personnel numbers that have the PROCESS flag set). The report can control the type of grouping using the PNPCE_GROUPING_FROM_PAYROLL flag (normal or payroll grouping) and using the PNPGPRSN (grouping reason) and PNPGPVAL (grouping value) parameters of the selection screen. The GET GROUP event is triggered for each group of personnel numbers determined. The GROUPING_REASON and GROUPING_VALUE components contain the grouping reason and grouping value of this group. The number of personnel numbers that belong to this group and that are processed subsequently is in PERNR_NUM. The included ALL_PERNR table contains a list of these personnel numbers with additional information. The SELECTED flag specifies whether the current personnel number was originally selected (flag is set) or was marked by the report as to be processed. GROUPING_BEGDA and GROUPING_ENDDA contain the validity period that the personnel number has for this grouping. The NO_AUTHORITY flag is set if there is insufficient authorization for a personnel number. This personnel number is not processed further. The SORT component defines a standard sort order for the personnel numbers of a group. The report can change this by overwriting the values. In this way, report and logical database communicate with each other, which controls the further processing sequence of the personnel numbers.
The GET PERAS event is then triggered for all personnel numbers of the group (with the exception of the personnel numbers for which no authorization exists) in the sequence defined by the SORT component (see above). The SELECTED, GROUPING_BEGDA, and GROUPING_ENDDA components have the same meaning here as with the GET GROUP event. The PROCESSED_BEFORE flag specifies whether the personnel number has already been processed once before (it is possible that the personnel number belongs to several groupings and has been therefore been processed several times).
Sort Order
You can sort the list of selected personnel numbers using the Sort function in the application toolbar. You can choose to include up to seven fields from infotype 0001 for the sort. Since several data records can exist for infotype 0001 for a personnel number, you also need to specify for period evaluations (not the case for key date evaluations) whether the sort should take place according to the values of the last or of the first data record in the person selection period.
In PNP mode, the sorted sequence determines exactly the sequence in which the GET PERAS event is called. In CE mode, the sort determines the sequence in which the GET PERSON event is called. The list of persons is created based on the (sorted) sequence of personnel numbers. If only one person exist for each selected personnel number, the sequence of persons corresponds exactly to the sequence of personnel numbers. However, if several selected personnel numbers lead to the same person, only the first personnel number determines the sort sequence of persons. All other personnel numbers only determine the sequence in which the GET PERAS event is subsequently called. Provided that the report does not require the personnel numbers to be resorted by manipulating the SORT component at the GET GROUP event (see above), the GET PERAS event is called for the personnel numbers of a person in the sequence in which the personnel numbers were (originally) sorted.
Retrieving Infotype Data Records
As well as triggering the GET PERSON, GET GROUP, and GET PERAS events, the logical database also provides the data records of the infotypes that are requested using the INFOTYPES statement. In the report, you must specify the INFOTYPES statements where the variable declarations are made. You should do this in any case before the first code is entered.
In principle, there are three types of INFOTYPES statements:
INFOTYPES nnnn
The nnnn infotype is provided with the data records of the current personnel number at the GET PERAS event. Only the data records that are in the evaluation period specified in the selection screen are provided ( this is different to PNP, which provides all data records by default). Alternatively, the report can specify which data records are to be provided using the RP_SET_DATA_INTERVAL, RP_SET_DATA_INTERVAL_INFTY, and RP_SET_DATA_INTERVAL_ALL macros.
INFOTYPES nnnn AS PERSON TABLE
The nnnn infotype is provided at the GET GROUP event with the data records of all personnel numbers that are in the included ALL_PERNRS table (of the GROUP structure) and for which authorization exists (NO_AUTHORITY flag is not set). Only the data records that are in the evaluation period specified in the selection screen are provided. Alternatively, the report can specify which data records are to be provided using the RP_SET_DATA_INTERVAL, RP_SET_DATA_INTERVAL_INFTY, and RP_SET_DATA_INTERVAL_ALL macros.
INFOTYPES nnnn AS PERSON TABLE MODE P
The nnnn infotype is provided at the GET PERSON event with the data records of all personnel numbers that are in the included ALL_PERNRS table (of the PERSON structure). No authorization check is performed and all existing data records are provided independent of how the evaluation period is defined in the selection screen. The use of the RP_SET_DATA_INTERVAL, RP_SET_DATA_INTERVAL_INFTY, and RP_SET_DATA_INTERVAL_AL macros also has no influence here.
Selection Options
You can use all the functions and selection options in the selection screen (initially) to select personnel numbers regardless of whether the report is running in PNP or CE mode. Only in CE mode, the persons belonging to these personnel numbers are then determined. The functions that PNPCE provides to restrict the selection are described in the following. The environment in which these functions are actually used depends on the report and its report category. You can assign a report category to a report in maintenance of report attributes (SE38, Attributes, Change button -> HR report category button). The customer can override this assignment. To do so, perform the Customizing activity under 'Personnel Management' -> 'Human Resources Information System' -> 'Reporting' -> 'Adjusting the Standard Selection Screen'. Follow the same path to define and change report categories in the Customizing activity. Since the PNP logical database also uses the concept of report categories, ensure that you assign only one report category that is created specially for the PNPCE database to a PNPCE report.
Selection Fields of the 0000 and 0001 Infotypes
You can use all the standard fields of the 0000 and 0001 infotypes for selection. You can also use additional selection fields that are the concatenation of two or more of these infotype fields. If possible, do not use these concatenated fields because they do not play a significant role in the selection and can lead to long runtimes in certain circumstances. You can show and hide the required selection fields using the Selection Fields function in the application toolbar. The report category defines a preselection of fields that should be available.
Dynamic Selections
The dynamic selections enable you to select according to any infotype fields and, in particular, according to customer-specific infotype fields. You can show and hide the dynamic selections using the Dynamic Selections function in the application toolbar. The report category controls whether this appears as a dialog box or inplace, that is whether the dynamic selections are supported at all. The basis for the dynamic selections is a selection view that defines which infotypes and which fields can be used for selection. You can define the selection view in the ABAP Workbench. You must choose For any table as the type of selection view (the For logical database type is not permitted although you may have presumed differently at first). The report category is used to control which selection view is used for the dynamic selections. If you use the dynamic selections, the Restrict by OrgStructure, Search Help, and Selection ID functions are not available.
Restrict by OrgStructure
You can also select personnel numbers by their position in the organizational structure. To do so, you use the OrgStructure function in the application toolbar. This button displays the organizational structure. Here you can select the organizational units to which the personnel numbers to be selected should belong. It is insignificant if the personnel numbers are assigned to the selected organizational unit directly or to one of its subordinate organizational units. If you restrict the selection by organizational structure, the Dynamic Selections, Search Help, and Selection ID functions are not available.
Search Help
You can use the included search helps of the PREM collective search help by clicking Search Help function in the application toolbar. You can also add customer-specific search helps here. For a description of how to do this, see the Customizing for Personnel Management -> Personnel Administration -> Basic Settings -> . Ensure that you also generate the selection program using the DBPNPGMC report so that the search help actually exists in the PNPCE logical database. If you use a search help, the Dynamic Selections, Restrict by OrgStructure, and Selection ID functions are not available.
Selection ID
You can also restrict the number of personnel numbers to be selected using a predefined selection method called a Selection ID. For information on how to use and create selection IDs, see the Customizing activity under 'Personnel Management' -> 'Human Resources Information System' -> . How you selection IDs is also described here. The selection IDs whose grouping is stored in the report category are available to you for selection on the PNPCE selection screen. When you select a selection ID, it is always performed. This happens either explicitly when you press the button (behind the selected selection ID), or implicitly when output starts (F8). If you use a selection ID, the Dynamic Selections, Restrict by OrgStructure, and Search Help functions are not available.
Evaluation Period
The PNPCE (and the PNP) differentiates between the data selection period and the person selection period. Both these periods are summarized in the term evaluation period. Whereas the person selection period affects the selection of personnel numbers, the data selection period controls the retrieval of data requested by the INFOTYPES statement. You can configure both separately on the selection screen by selecting an appropriate entry in each list box. Alternatively, you can set up both selection periods at the same time using a common list box. You can control which entries are in the list boxes (that is which evaluation intervals are supported) using the report category. The person selection period you have set up is taken into consideration when the personnel numbers are selected. Only the personnel numbers are selected that fulfill the selection conditions on at least one (key) date in the specified person selection period. All data records of the requested infotypes that are valid on at least one (key) date in the specified data selection period are retrieved by default for these personnel numbers. You can set up a different procedure using the RP_SET_DATA_INTERVAL, RP_SET_DATA_INTERVAL_INFTY, and RP_SET_DATA_INTERVAL_ALL macros. Retrieving data records for infotypes that were defined by the AS PERSON TABLE MODE P addition is an exception. In this case, all data records are retrieved independent of the data selection period.
The payroll period should be considered as a special feature for the evaluation period. You can select either the current payroll period or another payroll period. You must enter the payroll area in both cases. The evaluation period is calculated from these specifications. This interval is used as evaluation period (as person selection period and as data selection period) for the further (internal) processing.
The report can query the evaluation period used via the PN structure. The BEGDA and ENDDA contain the data selection period whereas BEGPS and ENDPS contain the person selection period. Inversely, the report can also set the data and person selection period explicitly. The report must also fill the relevant components of the PN structure at the START-OF-SELECTION event. This is only meaningful if the manual maintenance of the evaluation period was hidden using the report category.
Communication Between Report and PNPCE
The DBPNPCECOM include is an element of the PNPCE logical database. This is automatically included in each report that is based on PNPCE. The common part defined in this include means that the report and PNPCE have a common data area. This data area enables the data exchange for communication between the report and PNPCE. All switches that can be used by the report to control the process of PNPCE are defined here. The DBPNPCECOM include also contains a number of macros that PNPCE uses to make additional functions available to the report. Most of these macros were adopted by PNP and defined there in the DBPNPMAC include. Additional macros still exist in the TRMAC table, which has in the meanwhile become obsolete. Do not use these macros for any purpose. You can find all the macros defined in PNP that affect the functionality of the logical database in the DBPNPCECOM include. They have a slightly different spelling; underscore_ instead of hyphen-, for example RP_PROVIDE_FROM_LAST instead of PROVIDE-FROM-LAST. Some of the TRMAC macros in the DBPNPCECOM include were redefined with the same spelling but without the functionality so that any incorrect use (of the TRMAC macros) leads to a syntax error and is therefore excluded.
The following describes the functions made available by the switches and macros defined in the DBPNPCECOM include. For information about the exact syntax for calling a macro in view of its parameters and type specifications, see the definition of the macro in the DBPNPCECOM include.
Evaluation Period in the PN Structure
The PN structure contains information about the evaluation period for which the evaluation is started regardless of how this is specified on the selection screen. A report should access the fields of the PN structure only if it requires this information and should not access the PNPBEGDA, PNPENDDA, and other selection fields of the selection screen.
The PN-BEGPS and PN-ENDPS fields contain the person selection period for which the personnel number selection was performed. The PN-BEGDA and PN-ENDDA fields contain the data selection period. If you have specified the evaluation period using a payroll period, PN-PABRP contains the payroll period, PN-PABRJ the payroll year, and PN-PERMO the period parameters. The payroll period and payroll year are also in PN-PAPER.
The report can also fill the PN-BEGDA, PN-ENDDA, PN-BEGPS, and PN-ENDPS fields with values at the START-OF-SELECTION event and in doing so, specifies the evaluation period. In cases like this, it is not meaningful to have this setting option on the selection screen and it should therefore be hidden using the report category. In addition, the report must ensure that the values specified are valid since there is no longer a validation of these values.
Setting the Data Selection Period: RP_SET_DATA_INTERVAL, RP_SET_DATA_INTERVAL_INFTY, RP_SET_DATA_INTERVAL_ALL
The report uses the INFOTYPES statement to request infotype data records that are read and made available by PNPCE. The report can specify that it only requires data records that are valid in the specified period using the 'VALID FROM .. TO ..' addition. Unfortunately, you cannot use the 'VALID FROM .. TO ..' addition in most cases because it does not accept dynamic date specification. It only accepts constants. If you do not use the 'VALID FROM .. TO ..' addition, PNPCE returns all data records that are in the specified data selection period on the selection screen by default. If this is not required, the report can call the RP_SET_DATA_INTERVAL, RP_SET_DATA_INTERVAL_INFTY, and RP_SET_DATA_INTERVAL_ALL macros to restrict the infotype data records to a different validity period. The RP_SET_DATA_INTERVAL macro sets the validity period for an individual infotype whose name you specify in the first parameter. Do not confuse the name of the infotype, P0001 or PP0001 for example, with the number of the infotype 0001. You specify the validity period in the second and third parameters. You should use the RP_SET_DATA_INTERVAL_INFTY macro in the same way but instead of entering the name in the first parameter, enter the number of the infotype. Since the same infotype can be used several times (under different names) when you use the INFOTYPES additions 'AS PERSON TABLE' or 'NAME ...', this macro sets the validity period for all infotypes of the same number. In contrast, the RP_SET_DATA_INTERVAL_ALL macro only has the validity period as a parameter and sets this for all infotypes used.
Setting the Mode of an Infotype: PNP_SET_INFTY_MODE_BY_NAME, PNP_SET_INFTY_MODE_BY_NUMBER
The INFOTYPES statement can use the MODE addition to control whether the infotype should be processed and how this should proceed. If the addition is not used, this corresponds to a MODE Y and the PNPCE logical database reads the infotype and places it in the internal infotype table. MODE N enables the internal infotype table to be declared but no infotype data records are read by the PNPCE logical database. MODE P can only be used together with the 'AS PERSON TABLE' addition and causes all infotype data records of all personnel numbers of a person to be read at the GET PERSON event without authorization check or period restriction. The report can use the PNP_SET_INFTY_MODE_BY_NAME and PNP_SET_INFTY_MODE_BY_NUMBER macros to change the MODE specified by the INFOTYPES statement (dynamically) at runtime. The macros must be called at the INITIALIZATION or START-OF-SELECTION events. The PNP_SET_INFTY_MODE_BY_NAME macro sets the MODE for an individual infotype whose name you specify in the first parameter. Do not confuse the name of the infotype, P0001 or PP0001 for example, with the number of the infotype 0001 You should use the RP_SET_INFTY_MODE_BY_NUMBER macro in the same way but instead of entering the name in the first parameter, enter the number of the infotype. Since the same infotype can be used several times (under different names) when you use the INFOTYPES additions 'AS PERSON TABLE' or 'NAME ...', this macro sets the MODE for all infotypes of the same number.
Reading Time Management Infotypes: RP_READ_ALL_TIME_ITY, RP_READ_ALL_PERSON_TIME_ITY
Time management infotypes (2000-2999) often contain a large number of data records, particularly if positive recording is implemented. If a dataset that is too large is requested using the INFOTYPES statements, this can lead to performance problems or in an extreme case, to memory overflow. For this reason, there are the RP_READ_ALL_TIME_ITY and RP_READ_ALL_PERSON_TIME_ITY macros, which can be used to read time management data in a targeted manner. The time management infotypes are defined by the INFOTYPES statement with the MODE N addition. This enables the internal infotype table to be declared but no data is read (at the moment) by the PNPCE logical database. The report can then decide at the GET GROUP and GET PERAS events whether it wants to read the time management data and for which period. At the GET GROUP event, the report can call the RP_READ_ALL_PERSON_TIME_ITY macro to read all time management data on the personnel numbers of a person that should be processed. In other words, the time management data that is in the included ALL_PERNRS table of the GROUP structure. The data is then written to the infotypes that were declared by the INFOTYPES statement with the AS PERSON TABLE addition.
However, at the GET PERAS event, the report can call the RP_READ_ALL_TIME_ITY macro to read the time management data on the current personnel number. In both cases, you must specify the period in which the data records should be valid when the macro is called. The PNP-SW-IGNORELOCKEDRECORDS switch is also taken account of in both cases and controls whether locked data records are read or not. In addition, an authorization check is performed for all data records. If no authorization exists for a data record, this data record is rejected (that is, it is not placed in the infotype table). If data records are rejected because of missing authorization, the PNP-SW-AUTH-SKIPPED-RECORD global switch is set to 1. This switch is otherwise set to 0.
Locked Data Records: PNP-SW-IGNORELOCKEDRECORDS
In HR master data maintenance, you can lock individual infotype data records. These data records are normally ignored during evaluations using PNPCE. If you set the PNP-SW-IGNORELOCKEDRECORDS switch to N (at the INITIALIZATION or START-OF-SELECTION events), the report can however instruct PNPCE to read locked data records too.
Authorization Check: PNP_SW_SKIP_PERNR, PNP_GET_AUTH_SKIPPED_PERNRS
The PNPCE logical database performs an authorization check for all infotype data records that are requested by the report using the INFOTYPES statement. If no authorization exists for even one individual data record of one of the infotypes used, processing of the personnel numbers is terminated by default. In PNP mode, this means that the GET PERAS event (for the personnel number) is skipped. The report is only aware of this if it then (if possible at the END-OF-SELECTION event) calls the PNP_GET_AUTH_SKIPPED_PERNRS macro, which returns a list of the skipped personnel numbers.
In CE mode, the NO_AUTHORITY flag is set in the included ALL_PERNRS table at the GET GROUP event, which indicates to the report that no authorization exists. The following event, GET PERAS, is also not executed for this personnel number. As in PNP mode, the report can get a list of the personnel numbers for which no authorization exists using the PNP_GET_AUTH_SKIPPED_PERNRS macro.
You can enter different settings using the PNP_SW_SKIP_PERNR switch. If you set this switch (at the INITIALIZATION or START-OF-SELECTION events) to N, no more personnel numbers (without authorization) are skipped. Only the data records for which no authorization exists are rejected (that is, not made available). The report has no way of knowing that data records are being withheld from it.
Mass Access By Array-Fetch: PNPCE_ARRAY_FETCH_SIZE
The infotype data records are not read for each personnel number individually but in a mass access for several personnel numbers simultaneously. This reduces the number of database accesses and performance can be considerably improved. You cannot read the infotype data records of all personnel numbers at once since this can lead to problems with memory space depending on the number of selected personnel numbers and existing data records. For this reason, the personnel numbers are segmented into blocks of a fixed size and the personnel numbers of a block are always read together. The size of the block is set to 100 by default (this means that the personnel numbers from 100 persons are processed at the same time). The report can change this setting using the PNPCE_ARRAY_FETCH_SIZE switch at the INITIALIZATION or START-OF-SELECTION event. Be very careful if you change this value. If the value is set too high, it can lead to a memory overflow. If the value is too low, performance is affected. You must choose a suitable value based on the number of requested infotypes and their expected datasets.
Locking Persons/Personnel Numbers
By default, the logical database does not lock any personnel numbers or persons. However, the report can request this. In CE mode, the report must set the PNPCE_ENQUEUE_PERSONS switch to X. This enables the LDB to set locks for all personnel numbers of a person. The person is regarded as locked and is processed further only if all personnel numbers have been successfully locked. Otherwise, they are skipped. It is the reports task to remove this lock. To do so, the report calls the PNPCE_DEQUEUE_PERSON macro by specifying the person ID. Persons that could not be locked and were skipped are logged by the logical database. After processing has finished, the report can query this list using the PNPCE_GET_ENQ_FAILED_PERSONS macro. However, not all persons are logged, only the first N persons. The report can find out how many this is exactly using the PNPCE_LOG_ENQ_FAILED_PERSONS switch. 1 means that all persons should be logged. If the report calls the PNPCE_GET_ENQ_FAILED_PERSONS macro, the total number of skipped persons is returned with the first N logged persons.
In PNP mode, individual personnel numbers can be locked. The report (and PNP) must set the PNP-SW-ENQUEUPERNR switch to Y to enable this. The report is here also responsible for unlocking the personnel numbers and can call the PNP_DEQUEUE_PERNR macro for this by specifying the personnel number. The report can get a list of the personnel numbers that could not be locked by calling the PNP_GET_ENQ_FAILED_PERNRS macro. Only the first N personnel numbers and the total number of skipped personnel numbers are returned. The number of personnel numbers that should be logged can be specified using the PNP_LOG_ENQ_FAILED_PERNRS switch. 1 means that all personnel numbers should be logged.
Determining the First Data Record in the Period: RP_PROVIDE_FROM_FRST
The RP_PROVIDE_FROM_FRST macro analyzes the infotype data records that were transferred in an internal table to the macro with regard to the specified period. It places the first data record that is valid in the specified period (the data record with the lowest ENDDA) in the header of the internal table. If no data record exists in the specified period, the PNP-SW-FOUND global switch is set to 0. Otherwise it has the value 1. If the infotype contains subtypes, you also need to specify the subtype for which the last valid data record should be determined. If you do not specify the subtype, the result is undefined. In addition, the data records of the internal table must be sorted according to primary key. The data records are sorted if the data records were determined by PNPCE logical database using the INFOTYPES statement. Analyze the implementation of the macro if the exact functions of the macro are unclear. If in doubt, do not use the macro. Instead implement a suitable solution for the report in question.
Determining the Last Data Record in the Period: RP_PROVIDE_FROM_LAST
The RP_PROVIDE_FROM_LAST macro analyzes the infotype data records that were transferred in an internal table to the macro with regard to the specified period. It places the last data record that is valid in the specified period (the data record with the highest ENDDA) in the header of the internal table. If no data record exists in the specified period, the PNP-SW-FOUND global switch is set to 0. Otherwise it has the value 1. If the infotype contains subtypes, you also need to specify the subtype for which the last valid data record should be determined. If you do not specify the subtype, the result is undefined. In addition, the data records of the internal table must be sorted according to primary key. The data records are sorted if the data records were determined by PNPCE logical database using the INFOTYPES statement. A special feature of infotypes with time constraint 3 in this case is that the data record with the highest ENDDA is not necessarily returned, but the first data record (if it exists) that is valid on the end date of the specified period. Analyze the implementation of the macro if the exact functions of the macro are unclear. If in doubt, do not use the macro. Instead implement a suitable solution for the report in question.
Reading Infotypes: RP_READ_INFOTYPE
The RP_READ_INFOTYPE macro reads the data records of an infotype for the specified personnel numbers that are valid in the specified period, and writes these to the internal table specified. This table must be completed correctly. If no data records exist in the specified period, the PNP-SW-FOUND global switch is set to 0. Otherwise it has the value 1. In addition, an authorization check is performed for all data records. If no authorization exists for a data record, this data record is rejected (that is, it is not placed in the internal table). If data records are rejected because of missing authorization, the PNP-SW-AUTH-SKIPPED-RECORD global switch is set to 1. This switch is otherwise set to 0. The PNP-SW-IGNORELOCKEDRECORDS switch is also taken account of when the data records are read and controls whether locked data records are read or not.
Normally, infotypes are read using the HR_READ_INFOTYPE function module. The RP_READ_INFOTYPE macro can improve performance when the data records have already been read by PNPCE and are in the internal buffer. PNPCE only read the data records that were requested by the report using the INFOTYPES statement. In addition, the buffer is deleted again at the latest after 100 processed personnel numbers. If however the report requests the data records using an INFOTYPES statement, it is not particularly meaningful to request the data records again for the same personnel number using the RP_READ_INFOTYPE macro. The buffer is only useful when the data records are called for a different personnel number if these personnel numbers belong to the block of the 100 current buffered personnel numbers. Always weigh up the advantages of this macro against the consequences of its use for performance.
Excluding Withdrawn Employees: RP_SEL_EIN_AUS_INIT
If this macro is called at the INITIALIZATION event, only personnel numbers are selected that do not have the status withdrawn in the specified person selection period. From a technical point of view, the select option PNPSTAT2 (STAT2 from infotype 0000) is filled with '   0' for this. This is a default value for the selection condition displayed on the selection screen that the user can change or delete at a later date.
Progress Indicator: PNPCE_NO_PROGRESS_INDICATOR, PNPCE_PROGRESS_BLOCK_SIZE
The PNPCE logical database uses the standard technique of displaying processing progress (process indicator). If the report wants to set up its own progress indicator or does not want to have a progress indicator displayed, it can switch this indicator off by setting the PNPCE_NO_PROGRESS_INDICATOR switch to X. The PNPCE_PROGRESS_BLOCK_SIZE switch enables the report to control how often (that is, after how many processed persons) the progress indicator should be updated. If the progress indicator is updated too often, performance suffers.
Payroll Grouping: PNPCE_GROUPING_FROM_PAYROLL
If you set the switch to X, the grouping of personnel numbers (as returned at the GET GROUP event) should be performed on the basis of payroll data.
Personnel Numbers Skipped Due to Error: PNP_GET_ERR_SKIPPED_PERNRS
A special logic for determining data records is implemented in PNPCE for certain infotypes. This is performed using a function module (HR_COST_DISTRIBUTION_GET) for infotypes 0027 and 0266. In the case of an error, the function module can trigger an exception. PNPCE reacts to an exception by terminating processing of the personnel numbers for which the error occurred (that is, the PUT PERAS event is not triggered). If the report wants to know which personnel numbers were skipped due to this error, it can call the PNP_GET_ERR_SKIPPED_PERNRS macro.
Comments
Headers of Infotype Tables
PNPCE fills the table body with infotypes defined by INFOTYPES. It does not fill headers. These are initialized. Therefore, it is not permitted to program headers. This is in part different in the PNP logical database. In certain cases, the header is also filled but in many cases it is not filled. Since this depends on various factors, which, in particular, cannot be traced or controlled by the report, you are also not permitted to program headers.
Infotype Administration Table $RINFO$
In the $RINFO$ table, infotypes are managed that the report defines using the INFOTYPES statement. It is defined in the DBPNPCECOM include so that the report also has access to this table. You are forbidden to manually modify this table for the purpose of changing infotype characteristics by the report. Instead, use the macros that enable you to set the infotype characteristics (set the MODE by PNP_SET_INFTY_MODE_BY_NAME and PNP_SET_INFTY_MODE_BY_NUMBER; set the validity period by RP_SET_DATA_INTERVAL, RP_SET_DATA_INTERVAL_INFTY, and RP_SET_DATA_INTERVAL_ALL).
Starting a PNPCE Report Using Preselected Personnel Number Set/Person Set
You can also start a PNPCE report using an externally predefined personnel number set. You must provide the PNPINDEX parameter with the relevant personnel number when you call the report using SUBMIT. Since, technically speaking, the select option for PNPINDEX is hidden, you must specify the personnel numbers in a RANGE structure that consists of SIGN, OPTION, and LOW. For each personnel number, SIGN must contain the value I, OPTION the value EQ, and LOW the personnel number. For SUBMIT, the range table should be transferred to PNPINDEX by the IN operator.
Example:
RANGES: pernr_index FOR pernr-pernr.
CLEAR pernr_index.
pernr_index-sign = 'I'.
pernr_index-option = 'EQ'.
pernr_index-low = '00000815'.
APPEND pernr_index.
SUBMIT pnpce_report WITH pnpindex IN pernr_index.
If a set of personnel numbers is defined in this way, you cannot use the Dynamic Selections, Restrict by OrgStructure, Search Help, and Selection ID functions to (further) restrict the set of personnel numbers. However, the conditions entered for the selection fields of infotypes 0000 and 0001 are taken into account.
Similarly, you can start a PNPCE report with a specified set of persons. You must provide the PNPPERID parameter with the relevant person IDs when you call the report using SUBMIT. Unlike PNPINDEX, PNPPERID is not a range but is an internal table whose row type is the PERSONID data element.
Example:
DATA: personid_index TYPE STANDARD TABLE OF personid.
APPEND '00000815' TO personid_index.
SUBMIT pnpce_rerpot WITH pnpperid = personid_index.
If a set of persons is defined in this way, you cannot define a set of personnel numbers (using PNPINDEX) at the same time. Also in this case, you cannot use the Dynamic Selections, Restrict by OrgStructure, Search Help, and Selection ID functions to (further) restrict the set of personnel numbers.
Using Several Selection Options Simultaneously
In addition to selecting fields of infotypes 0000 and 0001 as described above, PNPCE offers six other options for selecting personnel numbers. They are selection using dynamic selections, using organizational structure, using search help, using selection ID, and by explicitly specifying a personnel number set in PNPINDEX or a person set in PNPPERID when you call the report. These six options exclude each other, that is you can only use one of these options at a time. Appropriate queries on the selection screen attempt to ensure this. It can happen in certain cases, however, that more than one of these functions is used (for example, when you call the PNPCE report by explicitly specifying a personnel number set in PNPINDEX as well as one of the variants to be used in which dynamic selections were also stored). In this case, only one function, which is the first function used, is taken into account with regard to the following sequence:
1.     Dynamic Selections
2.     Restrict by OrgStructure
3.     Search Help
4.     Selection ID
5.     Explicit Specification or Personnel Numbers in PNPINDEX
6.     Explicit Specification or Persons in PNPPERID
The personnel number set found this way is always restricted further by the selection conditions specified in the 0000 and 0001 infotypes.
Example
PNP Mode (without functions for evaluating concurrent employment)
TABLES: PERNR.
NODES: PERAS.
INFOTYPES: 0006 NAME P0006.
GET PERAS.
table P0006 is filled with infotype 0006 data of PERNR
stored in PERAS-PERNR
WRITE :/ PERAS-PERNR.
CE Mode (with function for evaluating concurrent employment)
TABLES: PERNR.
NODES: PERSON, GROUP, PERAS.
INFOTYPES: 0001 NAME ALL_0001 AS PERSON TABLE MODE P.
INFOTYPES: 0001 NAME PP0001 AS PERSON TABLE.
INFOTYPES: 0006 NAME P0006.
GET PERSON.
table ALL_0001 is filled with infotype 0001 data of all PERNRs
stored in PERSON-ALL_PERNRS without authority check !!!
WRITE :/ PERSON-OBJID.
GET GROUP.
table P0001 is filled with infotype 0001 data of all PERNRs
stored in GROUP-ALL_PERNRS
WRITE :/ GROUP-GROUPING_REASON, GROUP-GROUPING_VALUE.
GET PERAS.
table P0006 is filled with infotype 0006 data of PERNR
stored in PERAS-PERNR
WRITE :/ PERAS-PERNR.

Change of LDB from PNP to PNPCE

HI All,
I have a HR program where LDB PNP is used. Now I need to change the LDB from PNP to PNPCE. Can any one please tell me what are the mandatory change I need to do in the program after changing the LDB.
Thanks & Regards,
Arnab

Hi,
Purpose
The PNPCE logical database supports the evaluation of HR master data. It includes the functions of the PNP logical database and offers additional evaluation options. Therefore, you should use the PNPCE logical database instead of the PNP logical database for all new developments.
The enhanced functionality of PNPCE in comparison to PNP essentially concerns the evaluation of Concurrent Employment, that is the possibility to group evaluate several assignments/personnel numbers of a person. The new events 'GET PERSON' and 'GET GROUP' as well as an enhanced syntax for the INFOTYPES statement (addition AS PERSON TABLE) for the procurement of infotype data enable you to use the new functionality. The use of these new functions is optional. You can run a PNPCE report that does not use the new events and the addition for the INFOTYPES statement in a PNP-compatible session. Since the PNPCE also has an improved selection screen, each report benefits from this even if the report does not use the functions for evaluating Concurrent Employment.
Prerequisites
A report that wants to use the PNPCE must enter this in its report attributes under Logical database.
In addition, the PERNR structure must be declared in the report using the 'TABLES PERNR' statement. You can only use the PERNR structure again in certain circumstances. The use of the 'GET PERNR' event is therefore forbidden. Instead, use the 'GET PERAS' event. Except for the PERNR-PERNR component, all other components of the PERNR structure are no longer filled and have initial values. This kind of programming (with the exception of PERNR-PERNR) therefore not permitted.
In addition to the 'GET PERAS' event, you can also use the GET PERSON' and 'GET GROUP' events. To be able to use these events, you must declare them using the NODES statement (NODES PERSON', 'NODES GROUP', or. NODES PERAS').
Explanation of Terms
If the 'GET PERSON' and 'GET GROUP events and the 'AS PERSON TABLE' addition for the INFOTYPES statement are not used, the report indicates that it does not require the functionality for evaluating Concurrent Employment. In this case, the report runs in a PNP-compatible session. This is referred to as PNP mode in the following documentation. On the other hand, if the report uses the functionality for evaluating Concurrent Employment we refer to CE mode.
Features
Process of an Evaluation
The PNPCE selection screen offers you as standard a range of functions that you can use to restrict the personnel number and person selection. These are discussed in more detail in the following sections. The process is initially as follows regardless of whether the report runs in CE or PNP mode. All available functions and selection conditions leads to the selection of personnel numbers. If you use the sorting function, this set of personnel numbers is then sorted according to the sort criteria you selected. In PNP mode, the GET PERAS event is triggered as a result for each personnel number.
In CE mode, the persons belonging to the personnel numbers are determined first for all personnel numbers selected. The GET PERSON event is then triggered for each person. The person ID is specified in the OBJID component of the PERSON structure. PERNR_NUM contains the total number of personnel assignments (= personnel numbers) that this person has and the ALL_PERNRS table, which contains a list of these personnel numbers regardless of whether they were actually selected or not. The SELECTED flag is set to X for the personnel numbers selected. The flag is initial for all personnel numbers that are not selected. The PROCESS flag specifies whether the personnel number should be processed in the rest of the process. This flag is set to X by default for the personnel numbers selected. However, the report can set or delete this flag at the GET PERSON event for all personnel numbers. In this way, report and logical database communicate with each other which enables the report to control the rest of the process.
In the next step, the logical database groups all personnel numbers of a person that are to be processed (that is, all personnel numbers that have the PROCESS flag set). The report can control the type of grouping using the PNPCE_GROUPING_FROM_PAYROLL flag (normal or payroll grouping) and using the PNPGPRSN (grouping reason) and PNPGPVAL (grouping value) parameters of the selection screen. The GET GROUP event is triggered for each group of personnel numbers determined. The GROUPING_REASON and GROUPING_VALUE components contain the grouping reason and grouping value of this group. The number of personnel numbers that belong to this group and that are processed subsequently is in PERNR_NUM. The included ALL_PERNR table contains a list of these personnel numbers with additional information. The SELECTED flag specifies whether the current personnel number was originally selected (flag is set) or was marked by the report as to be processed. GROUPING_BEGDA and GROUPING_ENDDA contain the validity period that the personnel number has for this grouping. The NO_AUTHORITY flag is set if there is insufficient authorization for a personnel number. This personnel number is not processed further. The SORT component defines a standard sort order for the personnel numbers of a group. The report can change this by overwriting the values. In this way, report and logical database communicate with each other, which controls the further processing sequence of the personnel numbers.
The GET PERAS event is then triggered for all personnel numbers of the group (with the exception of the personnel numbers for which no authorization exists) in the sequence defined by the SORT component (see above). The SELECTED, GROUPING_BEGDA, and GROUPING_ENDDA components have the same meaning here as with the GET GROUP event. The PROCESSED_BEFORE flag specifies whether the personnel number has already been processed once before (it is possible that the personnel number belongs to several groupings and has been therefore been processed several times).
Thanks and Regards
Ravi

Cardinality vs multiplicity?

Hi,
I need to know the difference between cardinality and multiplicity. I tried to find answers on the internet, but mostly I got answers related to UML. But I need to know the difference between them in the context of a database or data modeling. Can anybody
please tell me the difference ( if possible with the help of an ER Diagram)?
Thanking You,
Abhilash D K

Hi Abhilash,
UML uses the term Multiplicity, whereas Data Modelling uses the term
Cardinality. They are for all intents and purposes, the same.
Cardinality (sometimes referred to as Ordinality) is what is used in ER modelling to "describe" a relationship between two Entities.
Take a look at the following reference for a good simple explanation of terms and their use.
ER Diagram Tutorial
John Sansom | SQL Server MCM
Blog |
Twitter | LinkedIn |
SQL Consulting

Help with a liquid image

Hi,
I am having a problem with an image stretching in IE6. The
image stretches beyond the height of the screen, but when i adjust
the window, the image corrects itself. The image works fine in
safari, firefox and other browsers.
Attached is the code - please help me...I am going insane!

Nothing should be above the doc type declaration, your script
should be
in the head section, fix that and it *might* work.
Steve
MzMelis wrote:
> Hi,
>
> I am having a problem with an image stretching in IE6.
The image stretches
> beyond the height of the screen, but when i adjust the
window, the image
> corrects itself. The image works fine in safari, firefox
and other browsers.
>
> Attached is the code - please help me...I am going
insane!
>
>
>
> <script type="text/javascript">
>
> function reflow() {
> var photo =
document.getElementById("maintext"><img
> src="images/2front_image_full.jpg");
> photo.style.border = photo.style.border;
> }
>
> window.onload = reflow;
>
> </script>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
> "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="
http://www.w3.org/1999/xhtml">
> <head>
> <meta name="description" content="south australia
companion card
> program"><meta name="keywords" content="disability
companion card application
> brochure affiliate south australia address apply carer
attendant care
> cardholder national disability services disabilities
support program">
> <meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />
> 
> <title>South Australia Companion Card | welcome to
the South Australian
> Companion Card website</title>
> 
> <link href="sa-screen.css" rel="stylesheet"
type="text/css" media="screen"/>
> <link href="sa-print.css" rel="stylesheet"
type="text/css" media="print" />
> <style type="text/css">
> 
> </style>
> <script type="text/javascript">
> 
> </script>
> 
> <style type="text/css">
> 
> </style>
> 
> </head>
> <body bgcolor="#FFFFFF">
>
>
> <div id="hdrlogo"><img
src="images/cc_banner_01.jpg" alt="Fair ticketing for
> people with disabilities" width="250" height="60"
border="0" /></div>
> <div id="wrapper">
> <div id="topgraphic">
> <div align="left"><img src="images/cc_logo.gif"
alt="Companion Card Logo"
> width="139" height="57" hspace="10" vspace="10"
/></div>
> </div>
> <div id="topnav"></div>
> <div id="leftnav">
> <p align="left"><a href="index.html"><img
src="images/house.png"
> width="16" height="16" hspace="5" border="0"
/>Home</a> <a
> href="about.htm"><img src="images/vcard.png"
width="16" height="16" hspace="5"
> border="0" />About Companion Card</a> <a
href="apply.htm"><img
> src="images/user_go.png" width="16" height="16"
hspace="5" border="0"
> />Applying for a Card</a> <a
href="how_where.htm"><img
> src="images/picture_go.png" width="16" height="16"
hspace="5" border="0" />How
> and where to use your card</a> <a
href="organisations.htm"><img
> src="images/building.png" width="16" height="16"
hspace="5" border="0"
> />Orgnisations and Business Affiliation</a>
<a href="publications.htm"><img
> src="images/page_white_go.png" width="16" height="16"
hspace="5" border="0"
> />Publications / Applications</a> <a
href="faq.htm"><img
> src="images/comments.png" width="16" height="16"
hspace="5" border="0"
> />FAQs</a> <a
href="explanation.htm"><img src="images/comment_edit.png"
> width="16" height="16" hspace="5" border="0"
/>Explanation of Terms</a> <a
> href="contact.htm"><img src="images/telephone.png"
width="16" height="16"
> hspace="5" border="0" />Contact Us</a> <a
href="linktosite.htm"><img
> src="images/link.png" width="16" height="16" hspace="5"
border="0" />Link to
> this site</a><a
href="disclaimer.htm"><img src="images/page_white_text.png"
> width="16" height="16" hspace="5" border="0"
/>Disclaimer</a> <a
> href="accessibility.htm"><img src="images/key.png"
width="16" height="16"
> hspace="5" border="0" />Accessibility Tips</a>
</p>
> <div id="left1">
> <div align="center">
> <p><a href="
http://www.ministers.sa.gov.au/index.php"><img
> src="images/sagovtlogo.gif" alt="Government of South
Australia" width="120"
> height="134" border="0" /></a></p>
> <p><a href="
http://www.nds.org.au/SA/default.htm"><img
> src="images/nds-SA.JPG" alt="National Disability
Services SA" width="105"
> height="73" border="0" /></a></p>
> </div>
> </div>
> <p align="left"> </p>
> </div>
> 
> <div id="maintext"><img
src="images/2front_image_full.jpg"
> alt="Welcome to the South Australian Companion Card "
width="600"
> height="385"></div>
> </div>
> </body>
> </html>
>

How to download explanation texts of Payment Terms.

Hi All MM Experts,
I am a ABAPer.One of the MM consultant in our project wants to download the payment terms with the explanation texts (which is usually in multi line) in OME2 transaction. I have tried table T052 and T052U but it didn't help.
Any pointers on the same will be highly appreciated.
Thanks in advance,
Saket

It creates the texts for the payment terms in the input table I_T052 using the text symbols in program SAPLFHL2.
It means you cannot download the text from any table directly.
you have to write a program to download it, in this program you have to execute the function module to get the texts.

Payment Term -- Explanation in ME23N

Hi friends need help
iam doing a report in which i have to display payment term explanation exactly as it is .
I tried by using ZFI_TEXT_ZTERM. and aslo treid to
pick it from T052 and T052u .. but iam unable to get it .
regards
will definetly reward points

Hi Farukh
try this:
DATA: BEGIN OF XT052.
        INCLUDE STRUCTURE T052.
DATA: END   OF XT052.
DATA: BEGIN OF ZTEXT OCCURS 0.
        INCLUDE STRUCTURE TTEXT.
DATA: END   OF ZTEXT.
SELECT * FROM T052 WHERE ZTERM IN S_ZTERM.
REFRESH: ZTEXT.
CLEAR:   ITAB, ZTEXT.
ITAB-ZTERM = T052-ZTERM.
XT052 = T052.
CALL FUNCTION 'FI_TEXT_ZTERM'
EXPORTING
I_T052 = XT052
TABLES
T_ZTEXT = ZTEXT.
loop at itab.
write: / ztext.
endloop.
endselect.
Regards, Dieter
Message was edited by: Dieter Gröhn

Explanation text in Payment term obb8

Hi ,
I have created a new payment term II50 - payable in 2 installments , 50% in advance and balance in 15 days after invoice.
How should I add text in the explanation field in OBB8 ?? This text field is not enabled . screenshot attached.

Hi
You need to populate payment terms
I hope this helps you
Regards
Eduardo

Explanation of First Payment Term

HI All,
I want to get the Explanation of First Payment Term from the Payment term definition,
Under the SPRO, I found the Technical Information showing table name R052, however, I cannot find it under SE16...
Does anyone know the table name, pls help.
Thanks.
Terry

Hi terry
Goto SE11 and enter R052, press display button. on next screen it will display R052 as structure, click on "WHERE USED" button, and select tables.
It will display all the tables containing R052 fields. Try to find out the required table among them.
Currently I don't have the SAP system, else I could have told you exact answer.
try and revert

Terms of use, explanation of points

The link to the community terms of use, and presumably to the explanation of the points system:
https://discussions.apple.com/static/apple/tutorial/tou.html
Is broken. Who would know how to fix it?
Thanks
HD

Thanks John, but that's a 404 for me too:
EDIT: It's Chrome. Both links work fine with Safari.
Thanks guys.
Message was edited by: HD

What is the Laymans Explanation of the Term BT Lin...

If someone could explain, in the simplest terms,
A. What is meant by "Linear Multicast Channels" (please no links !!) and what are its advantages over what we presently have with our present BT Vision service
B. Do any other providers use this system at the moment
C. (i) Do any BT Vision Boxes presently in use, use this system NOW. (ii ) if not, are any boxes already pre equiped NOW to be able to use this system when its rolled out, (iii) if so, which present boxes have this capability
I ask this basic question as this subject is often discussed on this forum and I haven't a clue what it really means.
Thanks
Solved!
Go to Solution.

A) Linear multicast channels are live broadcasts over the internet. So, for example, BBC1HD will be coming to you over the wire rather than the aerial. Multicast is a one to many transmission mechanism which means that the channel only has to be sent over the network once and anyone who wants it picks it up as it comes in. This is distinct from Unicast which means that each device which wants the broadcast has its own copy flying across the network which doesn't scale well for mass communication. Multicast needs specialised hardware on the network to make it happen.
B) There are other providers which offer live channels over the internet, but whether they're using uni- or multi-cast, I know not. I seem to be remember reading that the other providers don't allow recording of the channels (yet), however BT are going the whole hog and allowing 2 channels to be recorded. Things may have moved on, though, so willing to be corrected on the first bit.
C) Any of the boxes running the new software can be easily upgraded to get the multicast channels. There are people on this board who are receiving them. Any black boxes running the old software need to be upgraded to the new software first. Silver boxes can't run the necessary software. YouView boxes can't yet until the software is available later in the year.
Any further confusion, just ask.

Explanation of terms

Similar Messages

Maybe you are looking for