Fly Loss Calculation

We have one chemical compund say " A100". which is evaporated during process. Aprox 0.08% of total mass.
Now i want to calculate this fly loss without using MRP (as Client's Requirement). Because through the BOM i can calculate the 0.08% (Component scrap and Operational Scrap)
In material master though i put 0.08% at MRP view, system takes round value = 1% at the time of consumption.
please help me.

Friend
We have one chemical compund say " A100". which is evaporated during process. Aprox 0.08% of total mass.
Now i want to calculate this fly loss without using MRP (as Client's Requirement). Because through the BOM i can calculate the 0.08% (Component scrap and Operational Scrap)
In material master though i put 0.08% at MRP view, system takes round value = 1% at the time of consumption.
I hope this can be resolved through Classification
Maintain all of these mateial in batches (indicator in work scheduling view). Extend classification (Batch class). Create a class using tcode Cl01 and chracterstics using CT04 assign characterstics to class
ENJOY SAP
Regards

Similar Messages

Disable Gain/Loss calculation for Secondary Ledger (SLA)

Hi Apps Gurus,
Currently I have the following functional SLA requirement:
I need to disable the Gain/Loss calculation in Secondary (subledger type) Ledger for AR invoice receipts in local/ledger currency. Below is the example, as it works now:
In the source primary ledger, on the AR invoice Receipt, there is NO gain/loss line, when paying ledger currency invoice on different date. But in the subledger accounting for secondary ledger there is calculated Gain/Loss line:
Example with Invoice No: 77775 in Receivables:
o     Primary Ledger currency: AUD
o     Secondary Ledger currency: USD
o     Invoice currency: AUD
     Invoice accounting entries for Primary Ledger:
-     GL date: 19-DEC-2012
-     Australia Spot rate for Primary ledger
Accounted_Currency=AUD, Entered_Currency=AUD
Revenue: Accounted_CR=4500.00 Entered_CR=4500.00
Recoverable Tax: Accounted_CR=450.00 Entered_CR=450.00
Receivable: Accounted_DR=4950.00 Entered_DR=4950.00
     Invoice accounting entries for Secondary Ledger:
-     USA Spot rate for Secondary ledger
Accounted_Currency=USD, Entered_Currency=AUD
Revenue: Accounted_CR=4325.00 Entered_CR=4500.00
Recoverable Tax: Accounted_CR=435.00 Entered_CR=450.00
Receivable:     Accounted_DR=4760.00 Entered_DR=4950.00
     Receipt accounting entries for Primary Ledger:
-     GL date: 20-DEC-2012
-     Australia Spot rate for Primary ledger
Accounted_Currency=AUD, Entered_Currency=AUD
Cash: Accounted_DR=4950.00 Entered_DR=4950.00
Receivable:     Accounted_CR=4950.00 Entered_CR=4950.00
     Payment accounting entries for Secondary Ledger:
-     USA Spot rate for Secondary ledger
Accounted_Currency=USD, Entered_Currency=AUD
Cash: Accounted_DR=4855.00 Entered_DR=4950.00
Receivable:     Accounted_CR=4760.00 Entered_CR=4950.00
Exchange Gain: Accounted_CR=95.00 Entered_CR=0.00
And we do not need the Gain line, despite the Receivable account would not be closed for this AR Invoice in Secondary Ledger.
Is there any option, functional setup in SLA, to disable calculation of Gain/Loss in such cases?
Many thanks in advance!
Krasen

Hi Ivruksha,
Thank you for looking into this case.
Of course if the Invoice was in foreign currency, there have to be a Gain/Loss line in the Primary Ledger.
But provided that in the Primary Ledger for NON-foreign currency invoice there is no FX lines, we don’t need such in the Secondary Ledger too. It’s a quite strange requirement, given the fact that the Receivable account balance will NOT be closed for this Invoice in the Sec. Ledger:
Dr: (Invoice) 4760.00$ and Cr: (Receipt) 4855.00$
So on the receipt I need the following acc. Entries for the Sec. Ledger (USD)
Dr: Cash 4855.00$
     Cr: Receivable 4855.00$
It is normal to have such functional behavior, provided that for the similar case in Payables there is NO FX line. See the example with AP Invoice in Sec. Ledger (USD):
Invoice GL date: 19-Dec-2012
Dr: Item Expense 4500.00 AUD / 4725.59$
Dr: Recoverable Tax 450.00 AUD / 472.56$
Cr: Liability 4950.00 AUD / 5198.15$
Payment Gl date: 20-Dec-2012
Dr: Liability 4950.00 AUD / 5184.46$
Cr: Cash 4950.00 AUD / 5184.46$
Fully balanced acc. entries, while the Liability account is definitely not closed from the both GL entries, which is accepted for the Secondary Ledger.
Hope this clears a bit more the case. I’ll appreciate any useful suggestions.
Of course the using “special” account code combination for recording the FX Gain/Loss in Sec. Ledger in the Account Derivation Rule as an workaround is a good option, if there isn’t any other.
Thanks and regards
Krasen

'Calculated Result' (profit/loss) is not displayed in BW query (NW04s)

The hierachy for financial statement item (0GLACCEXT) contains the folowing nodes:
-> Stocholder's Equity
> Profit/Loss current year
> Calculated profit (0COA/0BSRESULT-)
> Calculated profit
> Calculated loss
> Calculated loss (0COA/0BSRESULT+)
When I run a balance sheet query against virtual cube 0FIGL_V11, I don't get any data for nodes 'Calculated profit' & 'Calculated loss'.

Dear gurus,
I am searching to solve the same issue you Raynald reported...
Unfortunately, despite the 0BAL_DEPEND information correctly updated, this note 0COA/0BSRESULT+) does not appear.
Everything looks OK on the configuration side...Anyone has an idea what could cause the calculation not to be done ?
PY

Settlement of Reserve for immenent loss to CO-PA

Hi Experts,
We are working on ECC6.0.
In projects system, while doing project settlement we are getting error saying Complete PA transfer structure PS message no. KD514. Diagnosis says There is no value field assignment for cost element 9020001000 / variance category POCL in PA transfer structure PS. Basically Cost element 9020001000 is Technical RA Cost Element in Result Analysis Version (t-code OKG2). If we assign some value field to cost element 9020001000, system is updating that value field by the amount of Reserve for Immanent Loss calculated at the time of Result Analysis. We dont want the value field to be updated by this Reserve for Immanent Loss at the time of Project Settlement. In Short we want that value of Reserve for Immanent Loss should not flow to CO-PA at all.
In Valuation method for Result Analysis (t-code OKG3- expert mode) we have given RA Type as E (Revenue-Based Results Analysis) and Profit Indicator as Q (Percentage-of-Completion). We want the percentage of completion to be calculated based on Revenue i.e. % of completion = Actual Revenue/ Planned Revenue. But the system is calculating % of completion based on costs i.e. % of completion = Actual Cost/ Planned Cost.
Please suggest:
1) What we need to do so that Reserve for Immenent Loss will not be transferred to COPA.
2) What we need to do so that % of completion will be calculated based on Revenue.
Thanks in advance for your reply.
Bijay

Hi,
I think the RA method you have selected is cost proportional that is why it is calcluating the POC based on the planned/actual cost. You should select the method "POC based on Revenue planned". (method 06)
Hemant

Foreign Currency exchange gain & loss

Dear expert,
I have a problem here, need help.
I have made the setting for foreign exchange gain/loss in OB09 and start to use f-28 for incoming payment.
When run the simulation, it gives me 2 lines of exchange gain/loss calculation. 1st line with amount zero (local currency) and 2nd line with the gain/loss amount.
I wonder why I have 2 lines of exchange gain/loss calculation?
Did I did something wrong or miss some specific setting?
Thanks in advance. will assign points

Hi Louis,
Please note the example below and you will understand why two line items are created:
Local currency - USD; foreign currency - GBP
Vendor invoice in foreign currency - 100GBP - Jan (Exchange rate: I GBP=2 USD)
Feb - You valuated the open item (Exchange rate: 1 GBP = 3 USD) with update principle
Entry: Unrealised exchange rate Debit 100 USD
          To Special balance sheet account Credit 100 USD
Payment made in march where the exchange rate is 1 GBP = 3.5 USD
Entry will be:
Vendor debit                               200 USD
Balance sheet account debit        100 USD
Realised exchange rate loss debit 50 USD
To bank                                       350 USD
Are you getting the above entry? If so, then the above scenario will explain your predicament.
Cheers!
Rajesh

HR-ABAP Material

Dear all,
Kindly Provide me HR-ABAP Material.
Points will be Awarded for sure...!!!

Hi
HR:
HR deals with the INFOTYPES which are similar to Tables in General ABAP.
There are different ways of fetching data from these infotypes.
There are different areas in HR LIKE Personal Admn, Orgn Management, Benefits, Time amangement, Event Management, Payroll etc
Infotypes for these areas are different from one another area.
storing of records data in each type of area is different
LDBS like PNP are used in HR programing.
Instead of Select.. we use some ROUTINES and PROVIDE..ENDPROVIDE.. etc
and in the case of Pay roll we use Clusters and we Import and Export them for data fetching.
On the whole Normal ABAP is different from HR abap.
For Personal Admn the Infotypes start with PA0000 to PA1999
Time Related Infotypes start with PA2000 to PA2999.
Orgn related Infotypes start with HRP1000 to HRP1999.
All custom developed infotypes stsrat with PA9000 onwards.
In payroll processing we use Clusters like PCL1,2,3 and 4.
Instead of Select query we use PROVIDE and ENDPROVIDE..
You have to assign a Logical Database in the attributes PNP.
Go through the SAp doc for HR programming and start doing.
http://www.sapdevelopment.co.uk/hr/hrhome.htm
See:
http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
sites regarding hr-abap:
http://www.sapdevelopment.co.uk/hr/hrhome.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPA/PAPA.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPD/PAPD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PYINT/PYINT_BASICS.pdf
http://www.atomhr.com/training/Technical_Topics_in_HR.htm
http://www.planetsap.com/hr_abap_main_page.htm
You can see some Standard Program examples in this one ...
http://www.sapdevelopment.co.uk/programs/programshr.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci1030179,00.html?Offer=SAlgwn12604#Certification
http://www.erpgenie.com/faq/hr.htm.
http://www.planetsap.com/hr_abap_main_page.htm
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/HR_tutorial.html
These are the FAQ's that might helps you as well.
http://www.sap-img.com/human/hr-faq.htm
http://www.sapgenie.com/faq/hr.htm
http://www.planetsap.com/hr_abap_main_page.htm
http://www.atomhr.com/library_full.htm
HR Long texts Upload
Look at the below link
Also,
Few notes are below:
InfoSets in the HR Application
You can use SAP Query in HR to report on HR data. Queries are maintained as described in Creating Queries. The special features of queries created for HR are described in Maintaining Queries in the Human Resources Application. The maintenance procedure for HR InfoSets differs from the described procedure inasmuch as HR data fields are grouped together in infotypes.
InfoSet management in SAP Query is also used for InfoSet Query. For further information, see Functions for Managing InfoSets.
If you want to create InfoSets for HR, you can use logical databases PNP, PNPCE, PAP, and PCH (see HR Logical Databases). The database you must use to create your InfoSet depends on the component in which the data you want to report on is stored.
The reports you can execute using InfoSets based on logical databases PNP (or PNPCE) or PCH are similar, but differ in that they can select different objects. The following table describes the connection between the logical database, and the infotypes you can include in an InfoSet. It also provides you with one or two examples of reports that you can execute using the appropriate InfoSets.
Logical database PNP/PNPCE* PCH PAP
Selection of Persons Objects from Personnel Planning Applicants
Infotypes that can be included in the InfoSet Infotypes for· Personnel Administration (0000-0999) · Time Management (2000-2999) · Payroll infotypes · Infotypes for Personnel Planning objects that can be related to persons If the object type is specified:· Infotypes for the object type · Infotypes for objects that can be related to the specified object typeIf the object type is not specified:· All infotypes · Infotypes for Recruitment (4000-4999)· Some infotypes for Personnel Administration (such as 0001 and 0002)
· Customer infotypes
Reporting examples · Selection of all persons who participated in a specific business event, output of prices for reserved business events · Selection of all persons assigned to a specific personnel area, output of qualifications held by these persons · Selection of all business events held in London in March, output of all persons who participated in these business events · Selection of all positions assigned to a specific organizational unit, output of all persons assigned to the positions · Selection of all applicants hired last year to work on special projects, output of addresses for the applicants selected
Logical database PNPCE (PNP Concurrent Employment) functions just like logical database PNP. The procedure for creating InfoSets is also the same. It only becomes significant if you work with Concurrent Employment.
Creating InfoSets
The maintenance procedure for HR InfoSets differs from the procedure described so far in this section inasmuch as HR data fields are grouped together in infotypes. To set up an InfoSet for the HR application, proceed as follows:
1. On the initial screen for maintaining InfoSets, enter a name for the InfoSet and choose Create.
2. On the next screen, enter a name for the InfoSet and select one of the HR logical databases in accordance with your reporting requirements.
Customer infotypes can be created on all HR logical databases. In each individual case, therefore, you must decide which database to select so that you can report on customer infotypes.
This screen enables you to enter an authorization group. All of the queries that are subsequently created using this InfoSet can only be executed by persons who have this authorization group.
3. Choose .
This takes you to the Infotype Selection for InfoSet screen. You now have the option of creating field groups and assigning fields as required for non-HR InfoSets. Field groups that correspond to infotypes and already contain fields, however, are always created for HR InfoSets. The field groups are displayed in an overview tree in the top right section of the screen.
The infotypes that you included in the InfoSet are displayed in an overview tree on the left of the screen. The infotype fields that are already included in field groups are displayed in a different color, and the corresponding field group ID is displayed.
In the standard system, a field group is created automatically for each infotype that you included in the InfoSet (a field group corresponds to an infotype).
In the standard system, each field group contains the infotype-specific fields. To ensure that working with the InfoSet is as easy as possible, you are advised to restrict your use of fields in each field group to those you really require. This means you should remove fields that are not required.
An infotype's fields must only be assigned to the pertinent field group. Make sure this assignment is correct. If the assignment is incorrect, the InfoSet could be rendered unusable.
When an InfoSet is created, the following fields are transferred automatically to the first field group:
§ Logical database PNPCE or PNP Personnel number
§ Logical database PAP Applicant number
§ Logical database PCH Object ID, plan version, and object type
6. Determine the fields that must be included in the field groups of your InfoSet. If you require further information, see Assigning Fields to a Field Group.
If you want, you can change the default sequence of field groups and fields as required using Drag&Drop.
7. To save the InfoSet, choose .
8. To generate the InfoSet, choose .
On the Change InfoSet (InfoSet name) screen, you can choose Edit ® Change infotype selection to add more infotypes to the InfoSet, or to remove infotypes from the InfoSet. Remember to regenerate the InfoSet afterwards.
This screen also enables you to update InfoSets if, for example, the system contains new additional fields for specific key values. To do so, choose InfoSet ® Additional functions ® Update additional HR fields.
9. Go back to the initial screen for InfoSet maintenance.
10. Choose User group assignment.
11. Select a user group, and save your entry.
sample code
START-OF-SELECTION.
GET pernr.
rp_provide_from_frst p0000 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
READ TABLE p0001 WITH KEY pernr = p0000-pernr.
if sy-subrc = 0.
write : p0001-plans. " earliest.
endif.
endif.
rp_provide_from_last p0014 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
READ TABLE p0014 WITH KEY pernr = p0000-pernr.
if sy-subrc = 0.
write : p0014-LGART. .
endif.
endif.
Also this is HR_data structure.
Enterprise Structure
Definition
Structure of company according to personnel administrative, time management and payroll perspectives from the point of view of your own company
The company structure describes elements of the company and there dependencies.
Structure
The enterprise structure in Personnel Administration consists of the following:
Client
The client is, in accordance with commercial law, an organizational and data technical isolated unit within the R/3 System, with separate master records and its own separate record of tables. A clients area of jurisdiction can correspond to a unit as small as a company, or as large as an entire enterprise.
Company code
The company code is the smallest organizational unit of external accounting in which a complete and isolated financial accounting can be created. All events that affect the company code and the creation of all statements for a legal financial statement, for example balances, profit and loss calculation are contained within the company code organizational units.
Personnel area
The personnel area is an organizational unit; according to a personnel administrative, time management and payroll organizational point of view, a personnel area represents a delimited enterprise area. The personnel area is only used in Personnel Administration and is unique within a client.
Personnel areas are sub-divided into personnel subareas. Organizational data and guidelines as how to assign it, are stored on a personnel area and personnel subarea level. The rules and guidelines could be of a legal, pay scale and collective agreement, or internal nature. A personnel area is assigned to a company code which has the financial accounting values that are relevant for the personnel area. A pay scale area, a pay scale type and a public holiday calendar are precisely defined for a personnel subarea.
Example
The personnel area in a software company can be subdivided into development, training and administration personnel subareas.
Personnel subarea
The personnel subarea is only used in Personnel Administration. The groupings linked to the personnel subarea determine which entries from the subsequent screen are allowed for an employee of a particular company code/personnel area.
Groupings are used for validation of master and time data. Groupings are also used to check the plausibility of data that you enter.
Organizational key
The organizational key enables you to define the organizational assignment more exactly. The organizational key can consist of elements from the enterprise structure and personnel structure.
If you require further information on the corporate structure, please see the Elements of the Enterprise Structure section.
Integration
The Hiring personnel action enables you to assign employees to the enterprise structure. The data is stored in the Organizational Assignment (0001) infotype. This infotype is essential for authorization checks.
http://help.sap.com/saphelp_47x200/helpdata/en/48/35c3ea4abf11d18a0f0000e816ae6e/frameset.htm
Personnel Structure
Definition
Describes an employees position in a company from the individual employees view.
Structure
The personnel structure can be considered from two perspectives:
administrative perspective
organizational perspective
The Structure link administrative personnel structure consists of the following elements:
Employee group
Employee subgroup
Payroll area
Organizational key
The extent of the distinction that you make between employee groups and employee subgroups depends on your evaluation and access protection requirements.
The organizational key consists of a part of both the enterprise structure and the personnel structure. The elements employee group and employee subgroup could also be relevant in forming the organizational key.
The Structure link organizational personnel structure consists of the following elements:
Position
Job
Organizational unit
Integration
To assign an employee to the personnel structure, use the Hiring personnel action. The data is stored in the Structure link Organizational Assignment (0001) infotype. This infotype is essential for authorization checks.
http://help.sap.com/saphelp_47x200/helpdata/en/48/35c3ea4abf11d18a0f0000e816ae6e/frameset.htm
kindly reward if found helpful.
kushagra

ABAP HR material

hi every one
Can any one help me in providing links for ABAP HR material
Rajesh

Hi Rajesh, read this.
HR:
HR deals with the INFOTYPES which are similar to Tables in General ABAP.
There are different ways of fetching data from these infotypes.
There are different areas in HR LIKE Personal Admn, Orgn Management, Benefits, Time amangement, Event Management, Payroll etc
Infotypes for these areas are different from one another area.
storing of records data in each type of area is different
LDBS like PNP are used in HR programing.
Instead of Select.. we use some ROUTINES and PROVIDE..ENDPROVIDE.. etc
and in the case of Pay roll we use Clusters and we Import and Export them for data fetching.
On the whole Normal ABAP is different from HR abap.
For Personal Admn the Infotypes start with PA0000 to PA1999
Time Related Infotypes start with PA2000 to PA2999.
Orgn related Infotypes start with HRP1000 to HRP1999.
All custom developed infotypes stsrat with PA9000 onwards.
In payroll processing we use Clusters like PCL1,2,3 and 4.
Instead of Select query we use PROVIDE and ENDPROVIDE..
You have to assign a Logical Database in the attributes PNP.
Go through the SAp doc for HR programming and start doing.
http://www.sapdevelopment.co.uk/hr/hrhome.htm
See:
http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
sites regarding hr-abap:
http://www.sapdevelopment.co.uk/hr/hrhome.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPA/PAPA.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPD/PAPD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PYINT/PYINT_BASICS.pdf
http://www.atomhr.com/training/Technical_Topics_in_HR.htm
http://www.planetsap.com/hr_abap_main_page.htm
You can see some Standard Program examples in this one ...
http://www.sapdevelopment.co.uk/programs/programshr.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci1030179,00.html?Offer=SAlgwn12604#Certification
http://www.erpgenie.com/faq/hr.htm.
http://www.planetsap.com/hr_abap_main_page.htm
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/HR_tutorial.html
These are the FAQ's that might helps you as well.
http://www.sap-img.com/human/hr-faq.htm
http://www.sapgenie.com/faq/hr.htm
http://www.planetsap.com/hr_abap_main_page.htm
http://www.atomhr.com/library_full.htm
HR Long texts Upload
Look at the below link
Also,
Few notes are below:
InfoSets in the HR Application
You can use SAP Query in HR to report on HR data. Queries are maintained as described in Creating Queries. The special features of queries created for HR are described in Maintaining Queries in the Human Resources Application. The maintenance procedure for HR InfoSets differs from the described procedure inasmuch as HR data fields are grouped together in infotypes.
InfoSet management in SAP Query is also used for InfoSet Query. For further information, see Functions for Managing InfoSets.
If you want to create InfoSets for HR, you can use logical databases PNP, PNPCE, PAP, and PCH (see HR Logical Databases). The database you must use to create your InfoSet depends on the component in which the data you want to report on is stored.
The reports you can execute using InfoSets based on logical databases PNP (or PNPCE) or PCH are similar, but differ in that they can select different objects. The following table describes the connection between the logical database, and the infotypes you can include in an InfoSet. It also provides you with one or two examples of reports that you can execute using the appropriate InfoSets.
Logical database PNP/PNPCE* PCH PAP
Selection of Persons Objects from Personnel Planning Applicants
Infotypes that can be included in the InfoSet Infotypes for· Personnel Administration (0000-0999) · Time Management (2000-2999) · Payroll infotypes · Infotypes for Personnel Planning objects that can be related to persons If the object type is specified:· Infotypes for the object type · Infotypes for objects that can be related to the specified object typeIf the object type is not specified:· All infotypes · Infotypes for Recruitment (4000-4999)· Some infotypes for Personnel Administration (such as 0001 and 0002)
· Customer infotypes
Reporting examples · Selection of all persons who participated in a specific business event, output of prices for reserved business events · Selection of all persons assigned to a specific personnel area, output of qualifications held by these persons · Selection of all business events held in London in March, output of all persons who participated in these business events · Selection of all positions assigned to a specific organizational unit, output of all persons assigned to the positions · Selection of all applicants hired last year to work on special projects, output of addresses for the applicants selected
Logical database PNPCE (PNP Concurrent Employment) functions just like logical database PNP. The procedure for creating InfoSets is also the same. It only becomes significant if you work with Concurrent Employment.
Creating InfoSets
The maintenance procedure for HR InfoSets differs from the procedure described so far in this section inasmuch as HR data fields are grouped together in infotypes. To set up an InfoSet for the HR application, proceed as follows:
1. On the initial screen for maintaining InfoSets, enter a name for the InfoSet and choose Create.
2. On the next screen, enter a name for the InfoSet and select one of the HR logical databases in accordance with your reporting requirements.
Customer infotypes can be created on all HR logical databases. In each individual case, therefore, you must decide which database to select so that you can report on customer infotypes.
This screen enables you to enter an authorization group. All of the queries that are subsequently created using this InfoSet can only be executed by persons who have this authorization group.
3. Choose .
This takes you to the Infotype Selection for InfoSet screen. You now have the option of creating field groups and assigning fields as required for non-HR InfoSets. Field groups that correspond to infotypes and already contain fields, however, are always created for HR InfoSets. The field groups are displayed in an overview tree in the top right section of the screen.
The infotypes that you included in the InfoSet are displayed in an overview tree on the left of the screen. The infotype fields that are already included in field groups are displayed in a different color, and the corresponding field group ID is displayed.
In the standard system, a field group is created automatically for each infotype that you included in the InfoSet (a field group corresponds to an infotype).
In the standard system, each field group contains the infotype-specific fields. To ensure that working with the InfoSet is as easy as possible, you are advised to restrict your use of fields in each field group to those you really require. This means you should remove fields that are not required.
An infotype's fields must only be assigned to the pertinent field group. Make sure this assignment is correct. If the assignment is incorrect, the InfoSet could be rendered unusable.
When an InfoSet is created, the following fields are transferred automatically to the first field group:
§ Logical database PNPCE or PNP Personnel number
§ Logical database PAP Applicant number
§ Logical database PCH Object ID, plan version, and object type
6. Determine the fields that must be included in the field groups of your InfoSet. If you require further information, see Assigning Fields to a Field Group.
If you want, you can change the default sequence of field groups and fields as required using Drag&Drop.
7. To save the InfoSet, choose .
8. To generate the InfoSet, choose .
On the Change InfoSet (InfoSet name) screen, you can choose Edit ® Change infotype selection to add more infotypes to the InfoSet, or to remove infotypes from the InfoSet. Remember to regenerate the InfoSet afterwards.
This screen also enables you to update InfoSets if, for example, the system contains new additional fields for specific key values. To do so, choose InfoSet ® Additional functions ® Update additional HR fields.
9. Go back to the initial screen for InfoSet maintenance.
10. Choose User group assignment.
11. Select a user group, and save your entry.
sample code
START-OF-SELECTION.
GET pernr.
rp_provide_from_frst p0000 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
      READ TABLE p0001 WITH KEY pernr = p0000-pernr.
     if sy-subrc = 0.
     write : p0001-plans. " earliest.
    endif.
endif.
rp_provide_from_last p0014 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
   READ TABLE p0014 WITH KEY pernr = p0000-pernr.
     if sy-subrc = 0.
     write : p0014-LGART. .
    endif.
endif.
Also this is HR_data structure.
Enterprise Structure
Definition
Structure of company according to personnel administrative, time management and payroll perspectives from the point of view of your own company
The company structure describes elements of the company and there dependencies.
Structure
The enterprise structure in Personnel Administration consists of the following:
Client
The client is, in accordance with commercial law, an organizational and data technical isolated unit within the R/3 System, with separate master records and its own separate record of tables. A clients area of jurisdiction can correspond to a unit as small as a company, or as large as an entire enterprise.
Company code
The company code is the smallest organizational unit of external accounting in which a complete and isolated financial accounting can be created. All events that affect the company code and the creation of all statements for a legal financial statement, for example balances, profit and loss calculation are contained within the company code organizational units.
Personnel area
The personnel area is an organizational unit; according to a personnel administrative, time management and payroll organizational point of view, a personnel area represents a delimited enterprise area. The personnel area is only used in Personnel Administration and is unique within a client.
Personnel areas are sub-divided into personnel subareas. Organizational data and guidelines as how to assign it, are stored on a personnel area and personnel subarea level. The rules and guidelines could be of a legal, pay scale and collective agreement, or internal nature. A personnel area is assigned to a company code which has the financial accounting values that are relevant for the personnel area. A pay scale area, a pay scale type and a public holiday calendar are precisely defined for a personnel subarea.
Example
The personnel area in a software company can be subdivided into development, training and administration personnel subareas.
Personnel subarea
The personnel subarea is only used in Personnel Administration. The groupings linked to the personnel subarea determine which entries from the subsequent screen are allowed for an employee of a particular company code/personnel area.
Groupings are used for validation of master and time data. Groupings are also used to check the plausibility of data that you enter.
Organizational key
The organizational key enables you to define the organizational assignment more exactly. The organizational key can consist of elements from the enterprise structure and personnel structure.
If you require further information on the corporate structure, please see the Elements of the Enterprise Structure section.
Integration
The Hiring personnel action enables you to assign employees to the enterprise structure. The data is stored in the Organizational Assignment (0001) infotype. This infotype is essential for authorization checks.
http://help.sap.com/saphelp_47x200/helpdata/en/48/35c3ea4abf11d18a0f0000e816ae6e/frameset.htm
Personnel Structure
Definition
Describes an employees position in a company from the individual employees view.
Structure
The personnel structure can be considered from two perspectives:
administrative perspective
organizational perspective
The Structure link administrative personnel structure consists of the following elements:
Employee group
Employee subgroup
Payroll area
Organizational key
The extent of the distinction that you make between employee groups and employee subgroups depends on your evaluation and access protection requirements.
The organizational key consists of a part of both the enterprise structure and the personnel structure. The elements employee group and employee subgroup could also be relevant in forming the organizational key.
The Structure link organizational personnel structure consists of the following elements:
Position
Job
Organizational unit
Integration
To assign an employee to the personnel structure, use the Hiring personnel action. The data is stored in the Structure link Organizational Assignment (0001) infotype. This infotype is essential for authorization checks.
http://help.sap.com/saphelp_47x200/helpdata/en/48/35c3ea4abf11d18a0f0000e816ae6e/frameset.htm
kindly reward if found helpful.
cheers,
Hema.

Standard Price for a Traded material?

Hi,
What are the pitfalls/disadvantages of defining the traded material at a Standard Price and not a moving average price. Details will be appreciated.
any relevant information will be usefull.
Thanks

Hi
If you are maintainnig a Standard price for the Trading material , then the Pricediffernce between the Material & the Purchase ptrice will be put into a different account.
When you sell the same material the profit will be calculated based on the Price of the material.
So if you are procuring the material at a higher price than the material price, in such case the material price is not updated & the Profit & loss calculations of the material will not be appropriate.
So it is better to alway use Moving average.
Thanks & regards
Kishore

Model KF based on loads from seperate sources

I need your thought for design options to implmenet following scenario.
I have two I.S having actual and planned data from R/3 and a Flat file. I also need another KeyFig updated into the target which is let's say difference of Planned & Actual. Assume, complexity of calculation for using this KeyFig doesn't allow to implement this as CalKfig at reporting level.
Should I model this in one cube or seperate cubes for Actual & plan and MultiCube on both?
If in single cube should I consider single keyFig with valuetype? or two seperate Actual and Planned keyfigs?
If Cal Kfig is updated like diff. of KFigs K1(Flatfile>>ODS) and K2(R/3 I.S), How to manage package sequence and ensure record availablity from both?
I will appreciate all resposes.

Hi Vishan
Usually in plan and actual scenarios....Actual will come from R/3 and plan will come from flat file...Its good to create two seperate cubes for actual and plan..Then you can create a multiprovider on both the cubes...Then you can calculate the difference b/w them on the fly using calculated keyfiugure or formula.
But see that your plan cube consists the char which exists in actual.
How frequently do your users execute this query. when you have 2 different sources, y do you want to make it complex. Ask your users how frequetly they release the budget. What kind of calculation do you want to make other then difference b/w actual and plan?
Regards
Rak
Message was edited by: Rakesh

Hr Structures

Hello experts,
1) I have a question. What is meant by Enterprise Structure? Personnel Structure?
I said it comprises of Company Code,Personnel Area, and Personnel Subarea and i explained briefly about these 3 and also I told the relationships like company to companycode, personal area to company code.I think the panelist is not satisfied with the answer. Do I need to add any thing else to this answer. Please help me.
Can any one explain the concept of Enterprise and personnel structures.(like how it related to employee structure and where we assign this to employees, and for what purpose we defining the Ent structure.)
Experts please help me.
Regards,
Ch.Goutam

hi cheeck this..
The enterprise structure in Personnel Administration consists of the following:
Client
The client is, in accordance with commercial law, an organizational and data technical
isolated unit within the R/3 System, with separate master records and its own separate
record of tables. A clients area of jurisdiction can correspond to a unit as small as a
company, or as large as an entire enterprise.
Company code
The company code is the smallest organizational unit of external accounting in which a
complete and isolated financial accounting can be created. All events that affect the
company code and the creation of all statements for a legal financial statement, for
example balances, profit and loss calculation are contained within the company code
organizational units.
Personnel area
The personnel area is an organizational unit; according to a personnel administrative,
time management and payroll organizational point of view, a personnel area represents a
delimited enterprise area. The personnel area is only used in Personnel Administration
and is unique within a client.
Personnel areas are sub-divided into personnel subareas. Organizational data and
guidelines as how to assign it, are stored on a personnel area and personnel subarea
level. The rules and guidelines could be of a legal, pay scale and collective agreement,
or internal nature. A personnel area is assigned to a company code which has the
financial accounting values that are relevant for the personnel area. A pay scale area, a
pay scale type and a public holiday calendar are precisely defined for a personnel
subarea.
The personnel area in a software company can be subdivided into development,
training and administration personnel subareas.
Personnel subarea
The personnel subarea is only used in Personnel Administration. The groupings linked to
the personnel subarea determine which entries from the subsequent screen are allowed
for an employee of a particular company code/personnel area.
Groupings are used for validation of master and time data. Groupings are also used to
check the plausibility of data that you enter.
SAP AG Personnel Administration (PA-PA)
Enterprise Structure
April 2001 29
Organizational key
The organizational key enables you to define the organizational assignment more
exactly. The organizational key can consist of elements from the enterprise structure and
personnel structure.
Personnel Structure
Definition
Describes an employees position in a company from the individual employees view.
Structure
The personnel structure can be considered from two perspectives:
administrative perspective
organizational perspective
The administrative personnel structure consists of the following elements:
Employee group
Employee subgroup
Payroll area
Organizational key
The extent of the distinction that you make between employee groups and employee subgroups
depends on your evaluation and access protection requirements.
The organizational key consists of a part of both the enterprise structure and the personnel
structure. The elements employee group and employee subgroup could also be relevant in
forming the organizational key.
The organizational personnel structure consists of the following elements:
Position
Job
Organizational unit
regards,
venkat

DIFFERENCE BETWEEN TALLY ERP AND SAP BUSINESS ONE

Hello Experts,
From where i can find the comparison between TAlly ERP and SAP business one ?

Tally 9.0
Accounting
. To fulfill legal requirements - records as per standards and practices
. To pay taxes to various bodies - statutory needs
. Keep the business running - manage receivables & payables, cash, bank...
. Keep a watch on the pulse of the organisation - key performance indicators
. Respond to queries - to locate the right transaction immediately
. With the entry of a voucher (this is what we call all accounting transactions) all books of accounts, all reports, all totals & sub-totals are updated instantly. There is nothing more that needs to be done - whether you are inserting a forgotten entry, or correcting one.
. Taxation requirements of all the states of India are available, in the prescribed formats.
. Supporting tasks like reminder letters, delayed interest, ageing, bank reconciliation.
. One single dashboard to look at all important business ratios.
. Drill down from any report, even the Balance Sheet, right to any voucher or filter and search.
. Data entry in the language of the users choice - and report in any other language (from the languages supported).
. Mark vouchers that are draft as 'optional' and convert these to final- with one button click
Financial Management & Controls
Tally.ERP 9 comes with rich features & financial reports that give you the necessary management and control of your business. A few of these are listed below:
u2022 Funds Flow & Cash Flow reports - help you locate bottlenecks
u2022 Bank reconciliation - keeps your bank books in sync, and identify unclear instruments
u2022 Customer Credit Limits - to limit risk of default and large losses
u2022 Budgets - keep tabs on projected expenses against actuals
u2022 Mark vouchers post dated - these will reflect into the books of accounts only on/after that date
u2022 For needs where reports have to consider a transaction that has not happened (say salaries for this month that get paid the next month) vouchers (called 'reversing journals') can be marked to 'disappear' for reports post a specific date
u2022 "Scenario" management - helps you with your business forecasting and planning. You can use optional, reversing journals and memorandum vouchers, to aid in recording provisional entries that are useful for interim reports
u2022 Multiple inventory valuation. You can decide one valuation method for the business, and be able generate financial reports using any other valuation method - as the  statutory method may not be appropriate for your needs, your bankers and for other decisions
u2022 Cash balances can go negative - you can get warned if this is about to happen, or see reports and make the necessary corrections
u2022 Several business exceptions are available (negative stocks, negative ledgers) - for
you to exercise control over these activities
u2022 A one-screen business ratios with drill down right up to the transactions - help you to correct course frequently u2022 Item wise & document wise profitability statements to control revenue leakage and inappropriate pricing
u2022 Internal audits are supported with audit controls - authorised users can mark vouchers as 'audited' and can get to see reports on changes made post audit, and the name of the person making the change
Inventory Accounting & Management
If you deal in goods, of any type, you'll appreciate the Inventory capabilities in Tally.ERP 9.
You can comprehensively record all types of inventory transactions, using goods receipt notes, delivery notes, stock journals, manufacturing journals and physical stock journals. All stock movements are fully recorded and maintained in stock registers.
Developed for all manufacturers, distributors, wholesalers or traders a small list of features are briefly described below:
Manufacturers:
. Bill of materials and Manufacturing Journals, to record material conversions
. Compound bill of materials support, for units that contain assemblies
. Multiple locations (godowns)
. Excise for manufacturers, including all documentation and invoice
. Costing for jobs
Distributors & Wholesalers:
. Multiple price lists, with effective dates of applicability
. Use multiple units of measure (say KG's & grams)
. Dual units of measure (say KG's and bags, to support variations as happens in commodities)
Traders:
. High speed billing, with support for POS printers
. Bar code support
. Automatic application of taxes
. Service billing & service tax
. Integrated sales return in bills
. Print bills (and any other document) in the customers language
Common:
. You can choose to de-link the computed inventory value to automatically appear in
   your financial statements - and enter this figure manually.
. Stock ageing reports, to identify slow and non-moving stocks
. Invoice profitability reports to keep a pulse on sales
. Multi-currency transactions - buy and sell across the world - with integrated forex  gain/loss calculations
. Physical stock take records to adjust physical vs. actual stocks
. Maintain batch & expiry details
Purchases & Payables: from Order to Payment
Tally.ERP 9 delivers the entire purchase cycle whether the need is the complete purchase order - goods receipt - rejections & returns - advances, debits & payments or a single payment entry, fulfilling all needs.
To ensure that you have the right stocks and minimize carrying costs, Tally.ERP 9 delivers the following to improve purchase orders:
. Define Re-order levels as a definite number or based on consumption
. Define minimum quantity to order as a definite number or based on consumption
. Pull up a report that shows the stock position, including complete details of open purchaseorders, sales orders that need to be fulfilled - check on past purchase history, and then place orders
. Optionally stagger delivery dates in the PO
When receiving goods:
. Make entries in accordance with supporting documentation, including errors your suppliers could have made (say of multiplication & round off)
. Incorporate additional costs
. Automatically manage input taxes
. Flexibility allows receipt of goods, quantities and rates different from that ordered - since this is common in real life
. Record samples & free items (using different 'actual' & 'billed' quantities)
. Multiple receipts for one order or one receipt for multiple orders, or against verbal ordersIn case there is a need to add other costs (say coolie and cartage) these additional charges can be apportioned to the cost of goods purchased.
Supplied goods may not match your needs and these are managed by the 'Rejections Out' inventory voucher. Supplier dues, input taxes and inventory positions are updated.
Suppliers often indicate likely profits, which may not be met. In case such assurances are made, you can look at Item profitability reports, and get the facts right. You could then negotiate a rebate and record this as a debit note.
Keep tabs of how much is due to whom, when. Manage advances, payables & post dated checks. Ensure there are no errors in payments - print checks from Tally.ERP 9.
Sales & Receivables: from Order to Receipt
The lifeline of a business, efficiencies in sales operations, both of goods & services, directly impact growth and profitability. The need to optimise and keep a close watch here requires exceptional capabilities from your business IT system - and Tally.ERP 9 meets these demands.
The sales process is supported with the following documents:
. Quotations - records of quotes
. Sales orders - accepted customer orders
. Deliver Notes - documents that accompany goods
. Sales Invoices/Cash Bill - to record the sale
. Credit Notes - for financial adjustments
. Rejections in - for goods returns
. Receipts - for advances and receipts
Do you have cash sales (sales across the counter)? With support for Point of Sale printers, bar codes and receipts in multiple tenders, you POS enable your business at no additional cost. Product sales may come with added services - and the integrated product & service billing will close this.
Enforce credit limits, where needed. Along with the Payment Performance of Debtors report you can identify persistent problems and take necessary business decisions. Interest for delays & reminder letters aid in collection.
For businesses engaged in Excisable goods, you get full support for Excise for Traders & Manufacturing Excise - matter of fact a business could be both!
Make multiple deliveries from one order, or one from multiple orders - this common need is available across all documents of the sales process.
Do you have multiple classes of customers? You can easily setup multiple prices (even in advance and specify the date from which they are effective).
Discounts against the line, or for the document, additional charges as a percentage or lump sum, automatic round off of bill totals, automatic computation of VAT & Service tax, returns & exchanges are all available.Need to verify that you are making the desired sales margins? Item wise and bill wise profitability reports will help you keep tabs.
Multi-company
Security: With multiple companies, possibly including personal accounts, you may need to control who gets access to which companies, and to do what. You can set up users, grant or deny access - and these are defined for each company.
Remote Access: You choose to specify which company is accessible remotely. You choose which remote users have access; you decide what access a remote user gets.
Central User Management: Users come and go. You might also have a password policy requiring users to change passwords every few weeks. You can take advantage of the ease of central user and password management that Tally.NET identities carry - and even remotely manage these while not in office.
Special NeedsMulti-CompanyMulti-PeriodMulti-Cost/Profit CentresMulti-CurrencyMulti-UnitsMulti-Location InventorySecurity and Access Control Remote Access
What is Series B
This Series will deliver major enhancements both in entirely new areas of functionality as well as in technology capabilities.
Technology & Capability Enhancements
Multi-session
Support for multiple application windows, which can even be launched by clicking on a mail link or a 'shortcut., Each of these are simultaneous 'windows' into different areas of your business processes & reports. Dynamic data refresh and the display of different views when resizing - for e.g. smaller windows displaying a more consolidated view of data, will improve organizational management and productivity.
Multi-threaded
A 'thread' is a specific task that is being performed by the microprocessor. Enhanced capabilities will be enabled such that each application window can perform more tasks simultaneously instead of linearly, including processing messages from the server. Multi-core processors, even on the desktop, are now common. We will take full advantage of these as well.
Multi Stack Architecture for Scale-up & Scale-down Deployments
To deliver the capabilities described above, and the ones that follow, Tally.ERP 9 will become 'componentised' - consisting of several layers of programs - often referred to as 'n-tier architecture'.
These software components are horizontally scalable, meaning that you can add one more computer to increase the computing power needed for a layer. In the same way, you can remove systems as needed, or collapse them into a single system - all of them even on a notebook, if required.
High Transaction Capacity with Low Latency & Management
Let us say that you start generating a report that needs to be extracted from a few thousand vouchers. This process is run in a 'session', which is isolated from all other users. Even if other users delete or modify any of the vouchers needed for the report while the report is being compiled, there is no impact on this session and you will get to see the report as if these other users did not exist.
In the same way, the user performing the edit will also be isolated. After the edit, he can open the voucher and see it with the changes he made, perhaps even delete it.
The architecture described above will in itself deliver substantial performance and transaction handling capacity. To push performance further in those cases when the storage media (typically the hard disk) is busy with other operations, additional capabilities will store these transactions 'temporarily' in a 'Q' for later write, while the user is free to continue his work (these transactions are protected against power failures and so on).
Payment Engine for Debit & Credit Cards
The facility for online payments using a variety of payment mechanisms (NEFT, online banking, credit cards), as well as receive payments (Debit / Credit Cards, NEFT etc) will be available.
Functional Enhancements
Online Banking and Reconciliation
Collaborating with Banks who wish to facilitate their customers with this capability, we will provide Online Banking - including Payment Instructions, Standing Instructions, DD, NEFT,RTGS Transfers, Balance Queries, Instruction Status, Automated or Semi-Automated Bank Reconciliation.
Point-of-Sale for most Retail Environments
Series B will support dedicated POS terminals, with Credit/Debit Card, Discount Coupons and various other payment mixes, Loyalty support, schemes, multi-layered supervisory control, simultaneous keyboard and scanner controls, integrated or isolated printing of bill and credit card authorisation slips, item substitution, rate markup/markdowns, integration with measuring devices - such as weighing scales, bill suspension and retrieval, bill reversals and cancellations, etc. It can also be used for other store operations (receipting, inventory management etc), and general business operations (finance and accounts) - both on the same machine or separate machines.
Income Tax
Comprehensive IT coverage encompassing corporate & individual income tax, including typical payroll requirements and e-Returns will be available.
EXIM Documentation
Import & export documentation has become a growing need with the world economy becoming more open. This requirement will be supported, additionally covering the processes that need to be managed along with the documentation.
Job Costing
The enhanced Job Costing functionality will support most job costing needs to a level of granularity that is increasingly needed. We expect that you will be able to handle most, if not all, project accounting needs as well.
Fixed Assets
To take advantage of tax breaks as well as to manage organizational assets, this feature will support all requirements - from opening assets, adding, removing, amalgamating, grouping, vendor tagging, AMC's, servicing, service calendars, repairs and upkeep, refurbishing, breaking-down, depreciating and disposal for complete fixed asset management.
Tally Addons Manufacturing Excise software, Tally Report Writer, Material Requirement Planning, Audit TrailVoucher-Type Level Security, SMS Plugin for Tally

"Process local xref/xwrite request" problem

Hi experts,
We set up a Planning application on (version 11.1.2.1) with 3 plan types.
I created a calc script in Plan type 1 to calculate currency calculation and aggregation only.
I fixed the range to contain only a few accounts within Plan type 1 and no xref formula, but when I trigger the script to run, it trigger "Process local xref/xwrite request" at the back and make the script run for very long time.
Did I miss anything? Or how can I fix the calculation to be done in Plan type 1 only?
Thanks!

This is the problem. I have fixed the account range to only 4 accounts for the calculation and make sure they all set to source plan type = Plan type 1. But when I fly the calculation, it still trigger this "Process local xref/xwrite request" session in essbase.
Did I miss any other step?
I search the web and seen people mentioning a UDA - "HSP_NOLINK". Do I need to assign it to account ranges that pointing to Plan type 2/3? My problem is, my fix (range) does not include such account. If I do need to assign it to Plan type 2/3 accounts, can I assign it to only the higher levels or do I have to assign it to individual level? Please kindly help!
Thanks!

Calculation of asset gain/loss amount

Hello gurus!
I'am trying to implement the asset retirement report (S_ALR_87012052) into SQL, but I am in trouble with the calculation of the GAIN and LOSS amounts of the asset. I already managed to find out the calculation methods of the other amounts using the ANEA table. I think that table should be used in theese two cases too. Can someone please help me?
Thank you
HM

Hi Marian,
Go to table ANLC and input BUKRS-company code, ANLN1-Asset no, GJAHR-Enter current fiscal year and AFABE-Depreciation area.
In output
Field KANSW is Gross block
Field KNAFA,KSAFA and KAAFA is Acc.dep up to FY start (Ord dep,Spl dep and Manual dep respectively)
Field NAFAG,SAFAG and MAFAG is Dep posted in current year.
So Net book value=KANSW-(KNAFA+KSAFA+KAAFA)-(NAFAG+SAFAG+MAFAG)
Profit/Loss=Sales revenue-Net book value.
Hope it is clear.
Regards,
G.Sethuraman

Tax not calculating for loss of pay on the reduced basic pay

Hi Experts,
We have an employee who has LOP for five days and hence the basic pay is reduced. However for tax calculation the system is not considering the reduced basic pay, it is considering the actual basic pay.
Eg
Employee X has 5 day Loss Of Pay for the month of May.
His actual Basic Pay is Rs 10,000
His Basic pay after considering the 5 day loss of pay is Rs 8,000 for the month May
For this particulat month system is calculating tax on actual Basic Pay i.e Rs 10,000. However we want the tax to be calculated on the reduced basic pay.
Please provide with your valuable inputs.
Thanks in Advance
Koutilya

Hi,
Tax is not calculated on the month salary. It is the annual salary on which tax is computed and deducted.
Annual salary gets stored in WT /410 (Regular Income) WT /411 (Irregular Income) and /413 (Perks).
Annual Regular income is computed as under:
Annual Reg Income = Regular Income Paid till last month + Regular Income for current month + Projected Regular income for balance months in the FY.
Check the values of these WTs in your case. These must be different in May from the values in April.
VK

I am trying to create a PDF document that calculates Gains and Losses in Mutual Funds. The calculation scripts are repetitive from line to line. The scripts work well until I reach the line 32. Script stops calculating...

I am trying to create a PDF document that calculates Gains and Losses in Mutual Funds. The calculation scripts are repetitive from line to line. The scripts work well until I reach the line 32. Although I am using the same script as the fields above in the columm, the script eventually stops calculating and I can't figure out why. Is there a limit of how many calculation scripts you can enter? I will attempt to attach my pdf as soon as I figure out how. Thanks.

For e31 :
var e30 = +getField("e30").value ;
var c31 = +getField("c31").value ;
if ( (e30 !== 0) && (c31 !== 0) ) event.value = e30 + c31 ;
else event.value = "";
for e32 :
var e31 = +getField("e31").value ;
var c32 = +getField("c32").value ;
if ( (e31 !== 0) && (c32 !== 0) ) event.value = e31 + c32 ;
else event.value = "";
for e33 :
var e32 = +getField("e32").value ;
var c33 = +getField("c33").value ;
if ( (e32 !== 0) && (c33 !== 0) ) event.value = e32 + c33 ;
else event.value = "";
Java console doesn't show any error... That's why I am wondering if it's not a limitation issue... or memory issue, because they are maybe too many rows or something....
The c value is not calculated.

Fly Loss Calculation

Similar Messages

Maybe you are looking for