IS-Retail:diff bet retail consignment process & rackjobber module

hi experts,
Can anyone tell me what's the difference between retail consignment process and rackjobbers module in SAP IS-Retail.Explain me the processes and there complete settings step by step in detailed.Thanks in advance.
Regards
Gopal

Hi Gopal,
Consignment Goods,
A consignment occurs when vendor provide article to a retailer (the u201Cconsigneeu201D), who agrees to pay vendor proceeds from the sales minus a commission. If vendor product doesnu2019t sell, the retailer(consignee) can return it.The Consignment processing in retail allows you to transfer the goods from your DC to any location and you have the flexibility to the convert the Stock type from consignment stock to any other stock its depends on the receipient.
Rack Jobber
Vendor provide the merchandise and rack directly in the retail location, and vendor work co-operatively with the retailer to share the profits.Thus relieving the retailer to acquire the merchandise and allow to gain from the sales of merchaside.Hope you understand.
Regards
Abdul

Similar Messages

Retail Inter company Consignment process-Help

Hi Everybody,
We need to implement the Inter Company Consignment Processs Between DC & Store since they belong to different company codes. The Process would be Consignment articles will be received from Vendor to DC >; then Intercompany Consignment PO from DC To Store >,Outbound delivery > Goods issue from DC > GR at Store > Sale from Store .
Need help for setting this up so that settlement works correctly -
1) What way it should be configured or processes should be followed so that Vendor Consignmnet stock is available in Store under the same Consignment vendor no through which DC procures consignment.
In our current prototye when the Stocks are being issue against Inter company Consignment PO from DC to Store & received at Store ,consignment stocks are posted under vendor no (DC) . Now how the consignment settlement work in this case as we would like to settle against the external vendor from whom DC procured consignment articles?
Are we doing correctly ? Or what should be the correct process ( config & relevent data) to support the Intercompany Consignment process ? We have maintained the other setting with reference to stock determination, article master settings etc.
Any help on this will be highly rewared as its the critical need of business,.
Pls share useful guidance to support the Intercompany Consignment process & settlement through sale at store .
WE also need to make the return process from store > DC > Vendor for customer return of consignment articles.
Pls share your experience or guidance on this....will be rewarded..
Thanks in advance for this.
Krish

Hi,
How did you solve the scenario can u explain.
Thanks
sreenivas

Retail Intercompany Consignment process

) What way it should be configured or processes should be followed so that Vendor Consignmnet stock is available in Store under the same Consignment vendor no through which DC procures consignment.
In our current prototye when the Stocks are being issue against Inter company Consignment PO from DC to Store & received at Store ,consignment stocks are posted under vendor no (DC) . Now how the consignment settlement work in this case as we would like to settle against the external vendor from whom DC procured consignment articles?
Are we doing correctly ? Or what should be the correct process ( config & relevent data) to support the Intercompany Consignment process ? We have maintained the other setting with reference to stock determination, article master settings etc.
Any help on this will be highly rewared as its the critical need of business,.
Pls share useful guidance to support the Intercompany Consignment process & settlement through sale at store .
WE also need to make the return process from store > DC > Vendor for customer return of consignment articles.
Pls share your experience or guidance on this....will be rewarded..
Thanks in advance for this.
Krish

resolved

Whats the diff bet Automatic Req Grouping & Grouping of SC for followondocs

Hi Friends
What is the diff bet Automatic Requirement Grouping and Grouping of SC for follow on documents
Regards
Vinny

Yes you are right, but the complete process is as below:
-> First Sourcing Should be activated in the SRM
-> Then when users creates SC with source of supply (or depending on sourcing config) the SC is moved to Sourcing Cockpit.
-> Then in the sourcing cockpit, the requirements are completed and submitted for grouping.
-> And then if the program BBP_SC_TRANSFER_GROUPED is executed, then the grouping happens for the follow on document.
Note: The technical scenario is also to be considered.
Hope this answers your question.
Regards
Kathirvel

Diff bet diff versions

Hi
Pls give me details of Diff. bet SAP 4.6 and ECC6.0
Aryan

Hi
/thread/170347
The only difference between ECC5 and ECC6 is that additional components like mySAPCRM, mySAPPLM, mySAPSCM, mySAPSRM are added in ECC6.0. HR was already a part of ECC5.0.
http://abdurohman.wordpress.com/2007/06/29/whats-new-in-ecc5-and-ecc6-ecc7/
Whats new in ECC5 and ECC6? ECC7?
Posted by abdurohman on June 29th, 2007
Other cross category docs: Miracleous Image and Qurans Mathematics | I want to visit Indonesian Computer Show
ECC stands for ERP Central Component / Enterprise Central Component, new version level of SAP R/3 ERP, the latest one as of June 2007 is ECC 6.0. They are also dubbed as SAP V5 and V6 or just SAP 5.0 or SAP 6.0. I think version transition time from ECC5 to ECC6 was too short, It seems like they just consolidated many component versioning in ECC6 with additional patches/support packages. I am sure it will be longer for (probably) ECC7 to come. I found at least 3 differences related to previous non-ECC version.
·     new in ECC5, BW (business warehouse or named BI / business intelligence in ECC6) is integrated with ERP. So probably you may have BW and ERP in one box if using ECC5 or ECC6. You can still have BW server without ERP component by installing Netweaver ABAP engine and additional BW components (as add-on and SP).
·     new in ECC5: double accounting, with double accounting you can have 2 or more ledgers in your ERP application, however in my experience in double accounting accounting using ECC5 (in one distribution company) there should be more effort and customer development if ERP going live time is different with double accounting going live time
·     Java kernel was introduced in addition to ABAP kernel. ABAP kernel still the main kernel for ERP function, however for other Netweaver package component like enterprise portal (EP), java kernel is main kernel. There is a configuration called double stack for a system that uses both ABAP+Java.
Additional notes for upgrade to new ECC:
·     might need new level of database version such as Oracle 10.1 or 10.2, there would be additional upgrade step for database
·     ECC needs more SAPS power and need re-sizing of our production SAP hardware
·     end of support maintenance for ECC 6.0 is 20013 (standard) and 2016 (extended), while 4.6C is 2006 and 2009, 4.7 is 2009 and 2012 (first quarter???)
·     there are table changes e.g. from enterprise 4.7 to ECC 5.0, there will be a lot of effort of customer program upgrade (Z* and Y* program which use the tables), however reimplementation is not suggested except there are a lot of issue son business process design on previous version and new business design is required
Short Difference between R/3 4.7, ECC5 & ECC6 !!!!!
1. SAP NetWeaver is SAP's technology platform. It has all of SAP's
technology in it. It is used to build and run SAP Applications and customer
applications (Application server, data warehouse, portal, coding, messaging,
etc). You can find more information on the SAP NetWeaver page on the SAP
Service Marketplace (http://service.sap.com/netweaver). Of course they is
also in on the SAP NetWeaver page in SDN.
2. ABAP is part of SAP NetWeaver. BW is part of SAP NetWeaver (as of
the 3.5release).
3. Prior to SAP NetWeaver, BW was a seperate product. It is shipped as part
of SAP NetWeaver since the SAP NetWeaver '04 release (SAP NetWeaver BI 3.5).
4. SAP ECC is part of the SAP ERP application (actually it is the minimal
installation of SAP ERP). SAP ERP runs on SAP NetWeaver. So when you get SAP
ERP you get SAP NetWeaver.
- SAP ECC 5.0 is part of SAP ERP 2004
- SAP ECC 6.0 is part of SAP ERP 6.0 (2005) [which runs on SAP
NetWeaver 7.0(2004s)]
5. SAP NetWeaver is delivered with SAP ERP so ABAP and the functional
modules are include in SAP ERP.
6. With SAP ERP (SAP ECC) you have a choice of activating BI within the SAP
ERP system or deploying in a seperate system. This is information is in the
SAP ERP master guides which can be found at
http://service.sap.com/instguides.
For SAP ERP 6.0 (ECC 6.0) it will the SAP NetWeaver 7.0 version of BI.
Vishal...

What is diff bet EDI and XI?

Hi Friends
What is diff bet EDI and XI?
Regards
Vinny Novice

"EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
The business data is saved in IDoc format in the IDoc Interface and is forwarded as IDocs. If an error occurs, exception handling is triggered using SAP tasks. The agents who are responsible for these tasks and have the relevant authorizations are defined in the IDoc Interface.
Features
The IDoc Interface supports three types of data flow with the external system:
·        Outbound processing
IDocs are transferred to a receiving system from your SAP System.
·        Inbound processing
IDocs are transferred to your SAP System from an upstream system.
·        Status processing
XI
SAP XI is based on general standards so as to enable external systems to be integrated. At the center of the infrastructure is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol). The application-specific contents are transferred in messages in user-defined XML (eXtensible Markup Language) schema from the sender to the receiver using the Integration Server.
●     Modeling and design of messages, transformations, and cross-component integration processes
●     Configuration options for managing collaborative processes and message flow
●     Runtime for message and process management
●     Adapter Engine for integrating heterogeneous system components
●     Central monitoring for monitoring message flow and processes
Thanks

Diff. bet Repetative & Descrete mfg.

hi...
whats the diff. bet Repetative & Descrete mfg.
can i get some detailed ldifference

please search in the forum..many threads with good explantiion available.
These are three ways of production in a industries can happen.
PP-discreet required where there will be discrete orders passing through a work center, here the capacity planning plays major role. i.e. if you have a lath machine, many orders are going through this lathe m/c and schedule plays very important role w.r.t lath as well as the product as the product has to go through many work centre. Every time the product many not be samecan be different, but same work center can be used for many products.
In PPPI- We are mainly concerned with quality parameters and Process management i.e control recipe is configured in this module. But the difference is the o/p is almost sameyou will not change the product, but every step is very impartment to achieve the product quality. And it is entered by operator and approved by shift supervisor through control recipe function.
REM- mainly to reduce the data input by person working in SAP and in this case we are bother about period end costing not the each order level costing as the process is repetitive and one order is sufficient for the wile life.

Diff bet BDC in appln & present

Gud morning guys,
hav a gr8 day
Coul any1 of u tel me diff bet BDC in application layer and presentation layer...
cheers
sakthi

Hi
Hope it will help you.
Reward if help.
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
The first is when application data to be replaced is transferred at once, and only once.
The second situation is to transfer data periodically from external systems to SAP and vice versa.
There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
Flat file can be created in your hard disk as follows:
1 Vinod Hyderabad
2 Kavitha Secunderabad
3 Kishore Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
ID(10),
NAME(25),
CITY(25),
END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = C:\FF.TXT
FILE TYPE = ASC
TABLES
DATA_TAB = ITAB
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
OTHERS = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION BDC_OPEN_GROUP
EXPORTING
CLIENT = SY-MANDT
GROUP = POTHURI
HOLDDATE = DATE1
KEEP = X
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. Populating BDCDATA Table
CALL FUNCTION BDC_INSERT
EXPORTING
TCODE = TFBA
TABLES
DYNPROTAB = BDCTAB
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION BDC_CLOSE_GROUP
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
Endif.
Endif.
*& Form GENERATE_DATA
Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = X.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = SCUSTOM-ID
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = /5.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = X.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-NAME.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-CITY.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = SAVE.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. GENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, Populating BDCDATA Table
Call transaction TFBA using BCDDATA Mode A Update S.
REFRESH BDCTAB
ENDLOOP.

Excise invoice and sale tax applicable in consignment process

Hi,
How excise invoice and sale tax applicable in consignment process in below stages--
in consignment fill up,consignment issue,Return andpickup
Regards
Ishikesh

Hi,
You have to pass JV for 50 picked up items through J1IS. For this you have to create new subtransaction type type and accordingly maintain the G/L in the tax on goods movement settings for acoount determination node.
Regards,
Sagar Wairagade

Returnable packaging in customer consignment process

I have this scenario:
I have returnable packaging (drums) that have been setup as non valuated materials in SAP. The item category in deliveries in YB10.
These drums have serial numbers. Since some maintenance needs to be done on these drums from time to time, therefore, equipment's need to be created for the drums. The equipment number and serial number are the same and the serial number profile is setup in such a way that the equipment is created automatically when the serial number is created
When the drums are in stock, the status is ESTO
Now, in the normal order to cash process, this is what happens:
1) Sales order - order is created for a material
2) Delivery - The drums are added to the delivery along with the material through a packing proposal. A serial number is specified for the drum and the order is PGI'ed to the customer
At this point, the status of the equipment/serial number changes to ECUS
3) Billing - normal billing (drums are billed)
4) Return delivery YBG5 - the empty drum is accepted back into warehouse
After PGR, the status of the serial number changes back to ESTO
During the customer consignment process, this is what is happening:During the consignment fill up when stock goes from warehouse to customer, the status of the serial number is changing to ECUS
During consignment issue, since we can only issue whatever material is there, the same serial number that was used during fill up is being used
However, when we do a delivery against the consignment issue, we are getting an error that the status of the serial number is ECUS and it is not suitable for movement
Since consignment stock is still owned by the company until an consignment issue is done, I am wondering whether SAP is behaving correctly by changing the status of the serial umber to ECUS after the consignment fill up.
Is there a way to use the same serial number in the consignment issue as the consignment fill up?
Please reply urgently

Try the following
Go to OMWB transaction and simulate the posting using your plant, material and movement type
The simulation will show the standard postings based upon goods movement
E.G. 601 GBB VAX valuation class, account
Identify your accounts assigned to both sides of the posting and then you should be able to re-assign the g/l accounts to the appropriate modifier string within OBYC
Hope it helps
Steve

Consignment process-WBS ELEMENT

in consignment process,while doing consignment fill up,system has thrown the
error"missing data WBS ELEMENT" what this wbs element,how can i get it?

Hi,
WBS is required in order to plan and post revenue. Also in case of milestone billing, dates are copied from WBS in billing plan.
You can create single WBS thru tcode: CJ11. For simplicity you can give the sales order number as WBS number, enter a Project Profile.
Let me know if you face any issues. I assume that you are not interested in entire WBS structure and a single element will suffice.
Regards

Consignment process

Hi
Why SAP has suggested to assign standard pur organisation to plant for consignment process?
I understand that price maintained in inforecord at standard pur org level will be used for goods issue and settlement process.
Will the consignment process work if the standard pur org not assigned to plant and inforecord maintained at normal pur org with info category as consignment.
Thanks
Deepak

deepak tata wrote:
> Will the consignment process work if the standard pur org not assigned to plant and inforecord maintained at normal pur org with info category as consignment.
Hi,
When ever you perform a goods movement (Inventory management transaction like consumption to cost center 201 K movement type or transfer to own stock 411 K movement type ) SAP must verify that either you maintained info r record for your plant's standard P.Org otherwise system will not allow you.(issue an error message )
But if you do any other transaction like PO system will not check standard P.org
The main reason behind it SAP reads the material's price from info record maintain at Standard P.org for the material and vendor and also the TAX information ( and not from any other source )

Vendor consignment process.

Hi All,
We are going live next week and client has Vendor consignment process.
I'm looking for help on the following steps.
1.Vendor consignement a process steps
2.Account determination step(OBYC)
3.Accounting postings for vendor consignment(T-accounts)
Any help is appreciated.
Thanks,
Anusha

Anusha,
Activate Consignment inforecords using tcode OMEV. This activates the consignment prices to be picked up using the consignment info records.
configure a special procurement type using IMG->Production->MRP->Master Data->Define special procurement type.
In OBYC configure the consignment payables account (transaction KON).
Assign the special procurement type created in step 2 to all the materials that are to use the consignment process. This is done in the MRP2 view of the material master maintenance transaction
Create Consignment info record using tcode ME11. Select info category as consignment. Create general data, Purchase Org data and conditions. Conditions allow you to create time dependent prices.
Create PR/PO using the item category K. Due to the nature of these items, price is not applicable and so do not enter price. During consumption, the price will be picked from the consignment info record.
The following transactions are used in consignemnt MB54 - Consignment stock MRKO - Settle consignment liabilities. Consignment stocks are not included in the company stock valuation. It is normal, as the ownership is still with the vendor.
Thanks
Sri

Consignment Process Accounting Entries on AP and AR

Hi Gurus
Can you Please let me know the accounting entries in detail for the Consignment Process on AP and AR side?
Please rephrase me if the question is represented incorrect
I have never worked on the Consignment Process
I really appreciate for your helpful answers
Thanks
Regards,
Meenakshi.N

Vendor provides materials & stores them on your company premises. The vendor remains the legal owner of the material until you withdraw material from consignment stores. You need maintaion all like ME11,ME01 and account assignemnt for KON in OBYC.The steps ME51,ME21,MIGO,MB1A,MRKO
The Accounting Generated After GR/GI/Settlement are:
1.Goods Receipt
No Accounting Movement
2.Goods Issue
Consumption A/C: DR
Consignment (Liability Account ) Payable: CR
3.Consignment Settlement
Consignment (Liability Account ) Payable: DR
Vendor Account A/C: CR
Found it from the other link below Vendor Consignment
Thanks
Meenakshi.N

Consignment Process with ERS

Hi All,
Is it possible to do the Consignment Process with ERS ?
If yes, then what are the steps invloved in this process ?
Thanks & Regards,
Kiran.

No this is not possible. The reason for this is ERS is based on Goods Receipts and consignment is based on Goods Issues.
Frankly not sure why you would want both?
Sandra

IS-Retail:diff bet retail consignment process & rackjobber module

Similar Messages

Maybe you are looking for