Pseudo logic

[Former Member]

Hi Gurus,

What is meant by Pseudo logic and importance of this?

Thanks in advance.

venkat

[Former Member]

Hello Venkat,

In common parlance, the word pseudo is used to mark something as false, fraudulent, or pretending to be something it is not, whereas in computer terminology Pseudo-code/ logic (derived from pseudo and code) is a compact and informal high-level description of an algorithm that uses the structural conventions of programming languages, but omits detailed subroutines, variable declarations or language-specific syntax. The programming language is augmented with natural language descriptions of the details, where convenient.

Pseudo-code resembles, but should not be confused with, skeleton programs including dummy code, which can be compiled without errors. Flowcharts can be thought of as a graphical form of pseudo-code.

In ERP terms, Pseudo logic/code is generally used by the functional consultants to design the functional document which in turn is used by the technical consultant to design the Technical specification document and finally do the appropriate changes as part of development.

Regards,

Gauravjit.

Reward points if the explaination is helpful

[Former Member]

HI venkat,

Subroutine

Call up a submethod

The processing of the current PC method is interrupted and a submethod is carried out. At the end of this submethod, the call up method continues.

You can transfer up to 8 parameters when calling up a submethod. These values are assigned the pseudo-values types _P01 to _P08, after their previous values have been saved.In the submethod, _P01 to _P08 are replaced during the run time by operation parameter value type and value. If the submethod has finished, the previous values _P01 to _P08 are restored.This is a pseudo-operation (without code). The actual processing takes place in the interpreter.

Another example is that You now display the posting change notice. When you made the usage decision, the system generated a posting change notice for all items in the inspection lot (the sample in the work center and the rest of the inspection lot in the high rack storage area). You now need to create and confirm a (Pseudo) transfer order to close the activities from the WM perspective.

Another example is Transfer Line Items to Master Data

you copy the line items previously entered in the transfer table to the master data table of the correction items.

With the transfer, pseudo document numbers are assigned for the line items. The numbers come from the number range of the document type to be specified. An existing document type can be used for this or a document type that is used for the old data transfer.

The line items from the old data transfer are separately indicated in the master data screen of the correction items ("Acquisition of asset data from previous years").

You can repeat the transfer of the line items as often as required. Line items already processed are recognized, provided that they have not been deleted from the transfer table.

<b>**PLEASE REWARD POINTS IF THIS IS USEFUL FOR YOU**</b>

REGARDS

AK

[Former Member]

Hi venkat,

The logic used for getting a Call Bundling is by a pseudo code.

Call bundling improves the performance of instance BAPIs by bundling the individual BAPI calls in the update task. Because the individual BAPI calls are not bundled until they reach the update task, the programming model for BAPIs remains the same, except for one change to the update logic in the update modules.

To achieve call bundling, you have to modify and/or generate the following three components:

1. The BAPI

Each BAPI performs the necessary consistency checks and organizational operations, such as number assignment and lock management. If this application logic is passed free of errors, the update modules are called IN UPDATE TASK.

2. The update module

The enhancement to the programming model involves the update modules – specifically, the database accesses are no longer triggered directly; instead, the pending options are buffered in the function group memory, and a form routine is then called indirectly, "ON COMMIT", which means that the operations are all performed at the end of the update task.

3. The form routine

The form routine takes the set of flagged operations in the function group memory, and performs the update with only one database access, using techniques such as array insert.

The structure of the three components that are relevant for call bundling can be illustrated in pseudo-coding as follows:

1. The BAPI:

function bapi_<object>_create.

{consistency checks and error handling}

call <object>_post in update task

exporting

.

endfunction.

Please reward points if this is helpful.

regards

AK