Idocs diff btwn bd20 & bd87

hi guys wats the difference btwn, bd20 and bd87 t codes and wat is the purpose they r used in ale-idocs.
thaks in advance.......

Hi chaitanya ,
BD87- (Program-RBDMON00 )It is used to monitor the Status of IDOCs created .Also it can be used to process the IDOC , which are stuck up in the pipeline.
BD20- (Program-RBDAPP01) It is used to Inbound processing
(background and foreground ) of IDOCs ready for transfer.
I hope this solves ur problem.
Regards
Note: Reward if it helps

Similar Messages

What is the diff btwn Schedule & Delivery w.r.t MM Module?

Hi!
What is the diff btwn Schedule & Delivery w.r.t MM Module?
Regards,
Imran.

Return delivery and repair are different.
For repair please follow:
1) Decision must be taken whether the same material code to be returned after the repair work.
2) Decision must be taken whether value updation is required during return of material
3) Based on the two above decision create a new material type and material master with that new material type.
4) Check the OBYC SETTINGS FOR BSX,WRX,BSV,FRL,GBB.
5) Create subcontracting PO for the repaied material code where you isuue the material as a component which is needed to be repaired.
6) Isuue the material to the vendor wrt the PO with movement type 541 in MB1B.
7) After repairing receive the material through MIGO wrt PO.
8) Book the invoice through MIRO.
Regards,
Indranil

Diff btwn Grid and cluster

Hi,
what is the exact difference btwn Grid and cluster?

Read the following:
Diff btwn Grid and cluster
Simon

Diff Btwn 0CPQUABU and 0QUANT_B on Inventory

Hi Gurus,
what is the Diff Btwn 0CPQUABU and 0QUANT_B fields on Inventory Cubes.
I see 0CPQUABU assigned to 0RECTOTSTCK on the update rules of 2LIS_03_BX .
Any explaination on how the key figures , I mean stocks are calculated will be useful.
Sree
Message was edited by:
SreeRama
Message was edited by:
SreeRama

Vikash,
In case of ATP you are including the order line quantity that is being entered into consideration for calculating ATP (on the fly) where as the item supply demand will consider only scheduled order lines.
Also ATP check does the check for all the lines if the item has configuration (I believe). THis is not the case in the item supply demand. It is just doing the check only for that item.
Also ATP can be global. If you want to check the availablity of the item across your supply and demand network, you can do that (Global Order Promising). Supply Demand is purely inventory function. ATP is planning function.
These are few differences. There can be or are much more.
Take a look at the ASO_ATP_INT to get an idea how to do this. This is used in quote and iStore where customers can check themselves when the product is available using the date.
I suggest you use ATP functionality and not Supply demand logic.
Thanks
Nagamohan

Diff btwn STANDARD and SORTED tbls??

Hi Experts,
Just curious to know that, In Wht scenarios/requiremets, we need to create a internal table, like fillowing(or How they differ from TYPE STANDARD TABLE OF)??
<i><b>it_a504 TYPE SORTED TABLE OF a504 WITH UNIQUE KEY kunnr prodh.
      wa_a504 TYPE a504,</b></i>.
thanq
Message was edited by:
        Srikhar

mainly performance reason ,if you use sorted internal table then it will have good performance than standard intentable
The internal tables could be catogrised into two.
indexed   : standard and sorted tables.
nonindexed: hash tables.
standard table: it is the one we use generally.In this the data is not sorted and the only thing we can do is just process the data with out any restriction on it.
sorted tables: it works in two different manner.
                       Frist one: is similar to standard table but the only difference is the data will be filled in a particular manner either ascending or descending.
                      Second one: u can also fill the table keeping any field as primary key.now the data will be filled based on that particular key.
Hash tables:   u can use this when u want to fill your internal table avoiding the duplication of data.it never permits the duplicate record to be stored in a internal table
Thanks
seshu

IDOC- Diff. File format.xml.......Pls Help....

Hi,
My scenario is that from R/3, they are sending ZACKXI IDOC to XI. In XI we have imported an xml named ROWSET in External Definition. Now I have mapped ZACKXI with ROWSET as XI would be able to receive ROWSET format from R/3.
R/3>(ZACKXI IDOC)>(ROWSET.xml)-->XI.
I am using normat receiver File adapter and FTP as the protocol in the ID.
But Surprisingly, XI is receiving xml msg, but not ROWSET, it is receiving ZACKXI IDOC xml.That should not be case. XI has to receive the ROWSET.xml format from ZACKXI IDOC coming from R/3.
Pls reply what to do..How would I be able to solve my problem....
BR
Soumya

Hi,
In SXMB_MONI you can see both Payload.
One is IDOC and other is ROWSET.
It will execute succesfully if you add your interface mapping name in your interface determination.
Regards,
Akshay.
Mark your question as answered if it is solved.
Reward points if find useful.
Message was edited by:
Akshay Jamgaonkar

AP - Supplier Sites Invoice Tab - Diff Btwn Tax code and Line Level

Hi All,
In paybles options setup, the Invoice Tax calculation is set to LINE Level and Allow Tax Calculation Override check box is checked.
While Defining the supplier, in the Invoice Tab of Supplier Sites, I changed it from LINE Level to Tax Code and unchecked the Allow Tax Calculation Override and Distribution Amounts Include Tax check box is Checked.
How will this change Impact on while creating the Invoices. What will be the Diff when we change the Tax Calculation from LINE Level to TAX CODE.
Help Appreciated.
Thanks

user449960,
Your scenario is a functional issue, follow Sumit's advise. If you feel there is something related to OAF, put your thoughts here.
--Shiv

Diff btwn Comany Code and Buiness Area

Hi Frnds,
Can anyone please let me know the clear difference btwn company code and business area and what are the advantages and disadvantages of these organizational units ?
Under which cases we can go for having a company code and not business area?
Expecting answer ASAP
Thank you
Regards,
Sharon.

This could help you....Picked it up from some documentation I had...Hope it helps
A common requirement which seems to be of concern to some, is to be able to produce Financial Statements, specifically Balance Sheets by some entity other than the legal entity (I shall call this the SBU - Strategic Business Unit). These SBU's are either below the legal entity or sometimes run across the legal entities.
If this is a requirement on your project, the first step is not to take this 'stated' requirement entirely at face value.   Dig a little deeper - ask for examples of current reporting, use "what-ifs", to determine the real or practical requirement. Sometimes it is not a full Balance Sheet that is required, especially if the SBU's are not fully autonomous, but more specifically the ability to report some Balance Type information by SBU in order. For example to provide some ROI type reporting.
If this is the case, the options are broader and implementation and use may be simpler.
The options in SAP are to implement the SBU's as :
SAP Business Areas
SAP Company Codes, if they do not run across legal entities
SAP Profit Centres
These options are discussed below. Note that requirements or impacts in other modules must also be considered and may influence this decision. Organisation Structure and Integration must be properly understood.
1. SAP Business Areas
The SAP Business Area is an FI organisational element which is intended to provide Financial Statements below or across company codes. The standard GL, financial statement functionality and reporting all support this.
However it is important to understand how SAP implements this, because it is by no means the same as the company code. The following points must be noted:
SAP company code will always be in balance, all the time, document by document.   The SAP Business Area will not. IE: it is possible to post a DR to one Business Area and a CR to another, or to leave one line item with a blank business area.
Business Area is not a mandatory field. It is dangerous to attempt to force this. It is not always possible for the system to determine the appropriate business area, it will then post a blank business area (unless you have 'forced' a substitution, which often just has the effect of replacing 'blank' with some other default).
SAP 'rectifies' this out of balance situation by providing period end programs which 'clean up' and post adjusting journals or inter-business area journals depending on the situation. See the documentation on these period end programs in the GL module.
Reporting by Business Area is available during the month (albeit out of balance) and visible within GL accounts. Compare with Profit Centre implementation below.
2. SAP Company Codes, if they do not run across legal entities
This is potentially a dangerous route, because of the possible across the board impact on day to day operational transactions, not just in FI, but in other modules. 'Test' all scenarios. SAP intends the SAP company code to be implemented as the legal entity and thus there is fairly 'rigorous' functionality around the company code. If you decide to implement SBU's as SAP company codes, you want to be sure that the majority and the key business transactions will be within one SBU.
In order not to compromise legal entity reporting, you should only take this option if the SBU's are subsets of a single legal entity. You can then use the standard multi- company summarisation reporting, or the consolidation functionality to provide your legal entity reporting.
3. SAP Profit Centres
This could be a good option if you do not require full/rigorous balance sheet by SBU, but are looking for some ROI type information. Standard configuration exists to :
flow revenues and expenses automatically through to Profit Centres.   (Expenses via cost centres, and revenues through a fairly complex 'assignment to profit centre' configuration logic)
transfer at period end balance sheet info such as payable, receivable, fixed assets, material stocks and work in process
allow specification of additional Balance Sheet accounts to be transferred.   You must then ensure that a profit centre has been nominated on all the line items, or else a default profit centre will be used. The issues with some accounts here will be the same as with attempting to force or identify a business area. See above.
Standard reporting is available to do ROI reporting, however this will of course only be available after the period end programs have been.

Diff btwn SE54 n SM30

Hi
what is the exact difference btwn SM30 n SE54.
whats the exact purpose of Table Maintenence Gen. apart from mainting a Table that is adding a field n any changes to the table.

Hello,
the maintenance view allows a user to easily enter values into a table, e.g. the administrator enters values into a customising table.
SE54 is the developer tool to generate / change the maintenance view, which is a set of function modules and screens.
SM30 is the user / administrator tool to use the maintenance view. It internally calls the generated function modules and screens, but those details are hidden from the user.
One advantage is that if you use the maintenance view to enter values into a customising table and press SAVE, you will automatically get a popup asking for a customising transport.

Diff btwn Monitoring Template and Notification Rules

Can anyone tell me the difference btwn when I should use a Monitoring Template and when I should use Notification Rules? I understand that there is a calendar setup for Notification Rules, but other than that, when should I use which? They look like they do the same thing.

With Monitoring templates, you set them once and apply them to multiple targets across your entire enterprise. So it gvies you a faclity to standardise stuff. For instance, you can create one template each for different database environments (e.g Development, Testing and Production). So each time you discover a new databases, instead of going in to database t manually define new metrics for the lot, you simply apply your already created template to them. Another example advantage is that each time your team decides that all production database tablespaces should change from a Critical of 90% to 85%, you simply change the template and reapply instead of doing it one-by-one on each database.
With Notification Rules, you are choosing the targets and the conditions with which you want to receive notifications. For instance, you have set all your Critical and Warning thresholds for say % Tablespace Space Used. When this threshold is reached, you want to be notified using the notification method you have set. Say via email or sms. So you create a notification rule that includes this metric, specify the notification method and indicate which administrators receive that notification.

HI all pls give me diff btwn upload ws_upload and GUI Upload

HI All,
         pls give me difference between
        upload
        ws_upload and
        GUI Upload
Thanks & regards .
Bharat Kumar

Hi,
WS_* Function modules are replaced by GUI_* FMs from 4.7 SAP version.
GUI_* modules have additional parameters when compared with WS_* FMs.
Both FM are used for uploading data .
But ws_upload is obsolete now .
WS_UPLOAD and WS_DOWNLOAD, the function modules used until now are not part of the standard set of ABAP commands. They are used to display the file interface on the presentation server. WS_UPLOAD and WS_DOWNLOAD are not compatible with USs and have been replaced by GUI_UPLOAD and GUI_DOWNLOAD.
The new function modules, GUI_UPLOAD and GUI_DOWNLOAD, have an interface that also allows you to write Unicode format to the local hard drive. For a description of these interfaces, refer to the documentation for each function module, available under SAP Easy Access " Development " Function Builder " Goto " Documentation.
WS_UPLOAD, GUI_UPLOAD FMs are used in BDCs.
WS_UPLOAD loads files from the Presentation Server to Internal ABAP Tables.
This is used upto SAP 4.6 version.
GUI_UPLOAD is used to loads a file from the PC to the server. The data can be
transferred in binary or text format. Numbers and data fields can be
interpreted according to the user settings.
You can check this for some info
http://help.sap.com/saphelp_erp2005/helpdata/en/79/c554a3b3dc11d5993800508b6b8b11/frameset.htm
http://www.sapdevelopment.co.uk/file/file_otherpc.htm
Regards,
Priyanka.

Diff btwn Oracle 8i Rowid & Oracle 9i Rowid?

Hi
Experts recently i was going through a document on Oracle where i came to know that the rowid of Oracle 8i & 9i Differs. As far as my obeservation is concerned i found that the length field of Rowid differs so can anyone explain me the contents of Rowid.
Ur help is highly appreciated.
Cheerz mate.

Rowid is like a column that return's a row address; it is usually unique.
It contains:
The data object number of the object
Which data block in the datafile
Which row in the data block (first row is 0)
Which datafile (first file is 1). The file number is relative to the tablespace.
To learn more read the Oracle Sql Reference
http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96540.pdf

Diff btwn contracts and scheduling agreements????

hi buddies.....
i have facing this question in lot of interviews but cant able to answer properly....
plz gimme some interview point of view answers...
thanks in advance...
venkatesh.v

Outline agreements in procurement can be 2 types:
Contracts or Scheduling agreements.
Contract is where you have a contract with the vendor,may be a for a predetermined quantity or predefined value. So everytime you need the matl, you need to make PO ref the contract asking for the delivery of the matl. In such instance when PO is ref with contract its called contract release orders or call off orders.
Scheduling agreement is a long term purchase agreement, where you will keep issuing the delivery schedules whenever there is a change in requirement or at predetermined time intervals. The delivery schedule can be on hour/daily/weekly/monthly basis. But it will contain different zones viz. firm/tradeoff/Forecast. Firm zone schedules are confirmed requirement and need to be taken by ordered party. Tradeoff zone requirement is to purchase the raw materails and ordering party is liable to pay raw material cost, in case of requirement cancellation. Forecast zone requirement is to help the vendor to plan his requirements.
SA is also an agreement with the vendor for the supply of matl, may be a quanity or value. The delivery dates will be maintained in ME38 ref the SA which are called delivery schedules.So you can maintain the delivery schedule and communicate the vendor on Forecase basis or JIT basis. And when you need some more matl then will only create SA deliveries using ME38. SA could be of 2 types:- without release documentation-system will transmit the delivery info to the vendor once you save the document.
With release documentation- after creating the delivery schedules you need to create SA release using ME84.
The main difference between contract and SA is volume of docs generated would be higher in contract since everytime you need to make a PO ref the contract and its time consuming, whereas SA can be integrated with MRP such that it automatically creates delivery schedules during MRP run provided if there is a requirement to the matl.
Visit : http://help.sap.com/saphelp_srm30/helpdata/en/7d/0a093f7c392e5ae10000000a114084/content.htm

FFT and Overall Values Differ btwn VI and DIAdem

Hi all,
I have an application that displays live vibration readings including the spectrum and overall vibration level. All my report generation is done in DIAdem scripts, so it's critical that any values calculated and displayed on the LabVIEW side match the values calculated and reported in DIAdem. The attached VI and Script, when fed the input from the attached TDMS file, give me significantly different values for the magnitude of the FFT and overall RMS value. Can anyone spot what I'm doing wrong?
Thanks,
Scott
CLAD
Solved!
Go to Solution.
Attachments:
FFT and RMS Script.VBS ‏5 KB
FFT and RMS VI.vi ‏39 KB
VibrationSample.tdms ‏103 KB

Hello,
Here is a great reponse from R&D. I felt it would be better to place this on the web then keep it limited to your service request.
The difference has to do with the Window-correction. The results are identical if you select rectangluar (or no) window.
Usually a Window is taking a part of the singnal away, so in the first place, the result has a different shape and is smaller compared to result with rectangular window. This can be corrected with a specific factor for each window.
There are two possible corrections. Random and periodic.
- Periodic is used if you have pure sine-wave like signals and you want to measure the peak value. A typical use case is the flattop-window which is designed for this type of calculations. The periodic correction is too large if you want to add the values to calculate the total RMS of the signal or of a the summation of a certain frequency band.
- Random is correcting the signal back to the correct overall RMS value and should be used in all other cases.
The periodic correction for the Hanning window is a factor of two. The random correction is about 1.633. DIAdem will give the same result as LabVIEW if you use the following correction type:
FFTWndCorrectTyp = "periodic"
In the world of FFT-analysis, the different corrections are very often not obvious and hidden to the user. Unfortunately this is also the case in LabVIEW. You can find a good example of an explanation here:
http://blog.prosig.com/2009/09/01/amplitude-and-energy-correction-a-brief-summary/
There are different factors for the different window functions. If you go deeper into the FFT-VI you will find the "Scaled Window VI". This has an output "window constants". With this, it is possible to get the correction values for the window functions.
I also think, that periodic is wrong in most cases when Hanning is used, because Hanning is best for the summation of RMS values in frequency bands and the results are wrong without a random correction.
Hope that helps.
Jacob R. | Applications Engineer | National Instruments

[SOLVED] bash - diff btwn 'normal' environment variables and VAR=x cmd

I always assumed variables passed like this:
VAR=value cmd
are passed to the program in the same way as environment variables. However; this is not the case; who can explain this?
$ svn commit
svn: E205007: Commit failed (details follow):
svn: E205007: Could not use external editor to fetch log message; consider setting the $SVN_EDITOR environment variable or using the --message (-m) or --file (-F) options
svn: E205007: None of the environment variables SVN_EDITOR, VISUAL or EDITOR are set, and no 'editor-cmd' run-time configuration option was found
$ VISUAL=$VISUAL svn commit
Sending file
Deleting file
Adding file
Transmitting file data ..
Last edited by Spider.007 (2014-04-24 17:55:49)

I'm curious too. I could at least *speculate* on how it could go wrong the other way around: if the envoked process spawns a new process that inherits a more general environment than the parent's, the first could work and the second could fail - but these results indeed should not happen.
Test code as evidence that the variables are passed in the same way:
#include <stdio.h>
int main(int argc, char **argv, char **env) {
char **envp;
for (envp = env; envp && *envp; envp++) printf("%s\n", *envp);
return 0;
Basically this is a very basic `env'. It shows all environment variables known to the process. No matter how they are set, they are all placed in env.
NOTE: most programs will use getenv() rather than the extra parameter to main(), but this is meant to test what is passed where.
Last edited by Trilby (2014-04-24 13:07:21)

Idocs diff btwn bd20 & bd87

Similar Messages

Maybe you are looking for