Skip to end of metadata
Go to start of metadata

Continues.. from Part-1

--> Name: should be in capital letters and doesn’t allow the special chars except under square (“__”)

    Type: means different solutions can develop here.

    Different Solutions are

  1. Integrated solutions
  2. Light weight solutions
  3. Mashups
  4. Addons
  5. Preconfigured solutions

-->There are different deployment units available means in which place you are going deploy which you have developed.

     There are some deployments: CRM, HCM, Financials, Foundation,  etc.

stage:
Now solution created with the name: ZERP_ARITHMET_77
-->The below screen you will find the screen name left side of the screen.

--> Automatically in development and business Configurations created. The screen should like this.. 

stage:
--> Right click in development the add the item.

stage:

--> Right click on *In Development  *add new item..the screen should like this below..

stage:
--> After clicking on new item it will open popup box within that in order to enter Business object name then click add button.

  Business object name shouldn't exceed 120 chars

 

--> If your were not following naming convention it will shown error popup..the screen should like this..

stage:

---> The initial screen should like this after creating new Bo named as Arithmetic(user specific)

Then write the code for BO (Arithmetic. Bo) as per for requirement. Here taken two variables and two actions. First two variables for input fields and third variable is for result.

Actions are    1.sum

                     2.Sub

import AP.Common.GDT as apCommonGDT;businessobject Arithmetic {        // Root node must not be specified, it is created implicitly        //        // Add elements here.         //         // To declare an element as alternative key, use the [AlternativeKey] annotation.        // Please note:        // - An alternative key of type UUID exists implicitly for each node, enabling the node        //   to be used as an association target.        // - The QueryByElements query is created automatically for each node.        // - Code completion is available with CTRL + SPACE.                        element number1:NumberValue;        element number2:NumberValue;                action sum;        action sub;                        element Result:DecimalValue;        }
import AP.Common.GDT as apCommonGDT;

businessobject Arithmetic

{

        // Root node must not be specified, it is created implicitly

        // Add elements here. 

        // To declare an element as alternative key, use the [AlternativeKey] annotation.

        // Please note:

        // - An alternative key of type UUID exists implicitly for each node, enabling the node

        //   to be used as an association target.

        // - The QueryByElements query is created automatically for each node.

        // - Code completion is available with CTRL + SPACE.

          

        element number1:NumberValue;

        element number2:NumberValue;

        action sum;

        action sub;

            

        element Result:DecimalValue;

        }


 




This Part Continues In Part--3 ...........

see below link (child pages ) for Continues of this one

  • No labels