flag

[Former Member]

in xk06 we delete a vender?what is mean by deletion of flag?

[Former Member]

Srinath,

When you delete vendor in concerned table the delition flag(a field in table ) will set to 'X'.Means to find how vendors deleted .

Ex: I a program you may need to select the vendors which are not deleted.That time this will come for use.

Don't forget to reward if useful....

[Former Member]

hi

it is deletion flag and not deletion of flag i guess.be clear if iam wrong.

May 14th, 2007

One problem with the network triggered by a SO with CN08 linkage. The network appears in display mode with system status -deletion flag active. How to change the system status and delete the network?

Here is the deletion flag behavior I have observed.

We are using assembly order processing and also use CN08.

Using CN22 or CJ20N to create DLFG you set the status on the network header Edit>status>deletion flag this rolls the status down to the activity level.

To reverse the deltion flag you must first:

cancel the deletion flag on the network header, then select all activities in the activity overview and cancel deletion flag.

Now some people believe that when the deletion flag is set that it removes all of the activities from the network.

This is false, users who do not see the activities after the deletion flag is set must use the following menu path to “reveal” the activties:

Edit> Object> Display Deleted>On

Which table is the system storing the Project Def, WBS, NW and NWA system and User status?

Check these tables:

PROJ : Master data for project definition

PRPS: Master data for WBS

PRHI: Master data for project Jerarquie

TJ02 - a list of all System Status’. You can use transaction BS23 to see these, or SE16n via normal enquiry

JEST - current System/ User Status by object number (WBS and Network)

JCDS - history of System/ User Status by object number (WBS and Network)

Needless to say, you have to get the object number first by looking at PROJ, PRPS for Projects and AUFK, AFKO, AFVC, AFVU or AFVV for Networks.

Use SE16n to see the contents.

PS: Status “code” contained in JEST for particular object number, after selecting object number of choice from JEST to obtain status text simply join JEST to TJ02T linking JEST-STAT to TJ02T-ISTAT

Purpose

Use this procedure to flag a customer master record for deletion.

Trigger

Perform this procedure when a request was received by the Customer Data Custodian from various departmental end users across the University to flag a customer master record for deletion.

Prerequisites

Customer does not have any open items on their account

Menu Path

Use the following menu path to begin this transaction:

· Select Accounting Financial Accounting Accounts Receivable Master records Set Deletion Indicator to go to the Customer Flag for Deletion: Initial Screen.

Transaction Code

XD06

Business Process Information

The business process supporting removing a customer master record from the SAP system is called archiving. The customer master data maintenance process will begin with a customer master data maintenance request form completed by the end users within various departments and sent to the Central Customer Data Custodian. The request form is used to request:

· New SAP customers

· Changes to existing SAP customers

· Requests to block or unblock SAP customers

· Requests to delete (mark for deletion or unmark for deletion) SAP customers

The request form will be a MS Word document. The form will be completed and e-mailed to the Customer Data Custodian. The Customer Data Custodian will review the request form. If there are any discrepancies on the form, the requestor is contacted for clarification.

Customer master records can be marked for deletion at different levels: (1) General level marks only the general data (address data) to be deleted and (2) Company code level, flags only the company code or accounting data to be deleted. This transaction, XD06 supports flagging both General and or Company code views for deletion.

The archiving process has several steps. (1) Customer's account is reviewed for open items such as invoices or credits. All open items on the customer's account must be cleared prior to archiving. (2) Customer's account is blocked from posting via transaction code FD05. This is done to prevent any new business posting to the customer's account. (3) Customer's account is marked for deletion via transaction code FD06. (4) Finally, the customer's master record is removed from the system via archiving program run. The archiving program is executed and managed by the Technical Support (BASIS) team. The archiving program only selects those records that are flagged for deletion

award points if helpful

[Former Member]

We can block the vendors in our business. we can block the vendor in all or certain company codes. if we use this vendor then it will give a mesage saying that vendor is marked for deletion.

we won't delete vendor just we mark the vendor for deletion.